homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients georg.brandl, neologix, pitrou, rhettinger, vstinner
Date 2011年11月29日.08:22:08
SpamBayes Score 6.830017e-05
Marked as misclassified No
Message-id <CAH_1eM0R_a6nbHEHW9B2UVUVFwriL=+AqsiKvcLtUTCbpKk7Kg@mail.gmail.com>
In-reply-to <1322520021.95.0.587171658447.issue13481@psf.upfronthosting.co.za>
Content
> Are CLOCK_MONOTONIC_RAW, CLOCK_MONOTONIC and CLOCK_REALTIME more accurate than gettimeofday (time.time)?
Actually, on Linux gettimeofday() returns CLOCK_REALTIME.
As for CLOCK_MONOTONIC{_RAW}, they're guaranteed not to go backward
(NTP and such).
But I think Antoine was referring to CPU time vs wall clock time (but
see comments above while this is probably a bad idea).
> I think this should be rejected.
Agreed.
History
Date User Action Args
2011年11月29日 08:22:09neologixsetrecipients: + neologix, georg.brandl, rhettinger, pitrou, vstinner
2011年11月29日 08:22:09neologixlinkissue13481 messages
2011年11月29日 08:22:08neologixcreate

AltStyle によって変換されたページ (->オリジナル) /