Victor Stinner victor.stinner at gmail.com
Thu Mar 15 01:29:35 CET 2012

• Previous message: [Python-Dev] Drop the new time.wallclock() function?
• Next message: [Python-Dev] Drop the new time.wallclock() function?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 14/03/2012 00:57, Victor Stinner wrote:
> I added two functions to the time module in Python 3.3: wallclock()
> and monotonic(). (...)

I merged the two functions into one function: time.steady(strict=False).

time.steady() should be monotonic most of the time, but may use a fallback.

time.steady(strict=True) fails with OSError or NotImplementedError if 
reading the monotonic clock failed or if no monotonic clock is available.

I patched the queue and threading modules to use time.steady() instead 
of time.time().

The documentation may need clarification.
http://docs.python.org/dev/library/time.html#time.steady

Victor

---

• Previous message: [Python-Dev] Drop the new time.wallclock() function?
• Next message: [Python-Dev] Drop the new time.wallclock() function?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list