[Python-Dev] this is why we shouldn't call it a "monotonic clock" (was: PEP 418 is too divisive and confusing and should be postponed)
solipsis at pitrou.net
Sun Apr 8 17:35:32 CEST 2012
On Sun, 8 Apr 2012 07:29:30 -0700
Guido van Rossum <guido at python.org> wrote:
> What to name it can't be decided this way, although I might put
> forward time.sleeptimer().
I would suggest timer() simply, but it's too close to time().
> I personally have a need for one potentially different clock -- to
> measure short intervals for benchmarks and profiling. This might be
> called time.performancetimer()?
It's called perf_counter() in the PEP:
More information about the Python-Dev