![](https://secure.gravatar.com/avatar/156a9300f7d83236d4edd631c779a14c.jpg?s=120&d=mm&r=g)
March 24, 2012
2:12 a.m.
On 3/23/2012 7:25 PM, Victor Stinner wrote: [snip]
- time.monotonic(): monotonic clock, its speed may or may not be adjusted by NTP but it only goes forward, may raise an OSError - time.steady(): monotonic clock or the realtime clock, depending on what is available on the platform (use monotonic in priority). may be adjusted by NTP or the system administrator, may go backward.
time.steady() is something like:
try: return time.monotonic() except (NotImplementError, OSError): return time.time()
I am surprised that a clock with the name time.steady() has a looser definition than one called time.monotonic(). To my mind a steady clock is by definition monotonic but a monotonic one may or may not be steady. Janzert