No method Profile.init()

[jiahao]

Long profiling runs may produce the warning

WARNING: The profile data buffer is full; profiling probably terminated
before your program finished. To profile for longer runs, call Profile.init()
with a larger buffer and/or larger delay.

However, the message is ambiguous and could be more helpful. There is no zero-argument method for Profile.init() (although there is a zero-argument method for Profile.__init__()), so the warning should tell users to run the two-argument method Profile.init(n, delay). However, since the warning does not print what the buffer size and delays were used in the run that triggered the message, this isn't very informative either.

cc: @Keno

[GunnarFarneback]

I've never been comfortable with the Profile.init function, especially that there's no obvious way to remember the order of the arguments. Maybe the no-argument call should report back current settings (and usage instructions?), whereas changing the settings should be done with keyword arguments.

[ivarne]

cc: @timholy

[timholy]

All good points. I'd have no objections to such changes. I'll tackle them soonish if no one beats me to it.