Victor Stinner victor.stinner at gmail.com
Sat Mar 24 11:37:07 CET 2012

• Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
• Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

>> - 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.
>>
>
> 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.

Do you suggest another name?

Victor

---

• Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
• Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list