[Python-Dev] Drop the new time.wallclock() function? (original) (raw)

Nadeem Vawda nadeem.vawda at gmail.com
Thu Mar 15 13:12:39 CET 2012

On Thu, Mar 15, 2012 at 1:10 PM, Paul Moore <p.f.moore at gmail.com> wrote:

Monotonic clocks are not necessarily hardware based, and may be adjusted forward by NTP. I appreciate that. But I'm still unclear how you would tell that had happened as part of the implementation. One call to the OS returns 12345. The next returns 13345. Is that because 100 ticks have passed, or because the clock "leapt forward"? With no point of reference, how can you tell?

The point (AIUI) is that you can't identify such adjustments (in the absence of some sort of log of NTP updates), so we should provide a mechanism that is guaranteed not to be affected by them.

Cheers, Nadeem

More information about the Python-Dev mailing list