[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)

Raymond Hettinger raymond.hettinger at gmail.com
Sun Apr 8 03:26:31 CEST 2012

Just to clarify my previous post.

It seems clear that benchmarking and timeout logic would benefit from a clock that cannot be adjusted by NTP.

I'm unclear on whether time.sleep() will be based on the same clock so that timeouts and sleeps are on the same basis.

For scheduling logic (such as the sched module), I would think that NTP adjusted time would be what you want.

I'm also unclear on the interactions between components implemented with different clocks
(for example, if my logs show three seconds between events and a 10-second time-out exception occurs, is that confusing)?


More information about the Python-Dev mailing list