(original) (raw)

On Mar 20, 2012, at 3:33 AM, Matt Joiner wrote:

I believe we should make a monotonic\_time method that assures monotonicity and be done with it. Forward steadiness can not be guaranteed. No parameters.

I think this discussion has veered off a bit into the overly-theoretical. Python cannot really "guarantee" anything here; alternately, it guarantees everything, since if you don't like what Python gives you you can always get your money back :). It's the OS's job to guarantee things. We can all agree that a monotonic clock of some sort is useful.

However, maybe my application wants CLOCK\_MONOTONIC and maybe it wants CLOCK\_MONOTONIC\_RAW. Sometimes I want GetTickCount64 and sometimes I want QueryUnbiasedInterruptTime. While these distinctions are probably useless to most applications, they may be of interest to some, and Python really shouldn't make it unduly difficult to get at them.

-glyph