[Python-Dev] Drop the new time.wallclock() function? (original) (raw)
Lennart Regebro regebro at gmail.com
Thu Mar 15 05:44:00 CET 2012
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] Drop the new time.wallclock() function?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Mar 15, 2012 at 02:58, Matt Joiner <anacrolix at gmail.com> wrote:
Victor, I think that steady can always be monotonic, there are time sources enough to ensure this on the platforms I am aware of. Strict in this sense refers to not being adjusted forward, i.e. CLOCKMONOTONIC vs CLOCKMONOTONICRAW.
Non monotonicity of this call should be considered a bug. Strict would be used for profiling where forward leaps would disqualify the timing.
This makes sense to me.
//Lennart
- Previous message: [Python-Dev] Drop the new time.wallclock() function?
- Next message: [Python-Dev] Drop the new time.wallclock() function?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]