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 vstinner
Recipients belopolsky, vstinner
Date 2012-01-24.00:22:28
SpamBayes Score 2.4590113e-06
Marked as misclassified No
Message-id <>
After time.wallclock() (issue #10278), let add a time.monotomic() function. It is similar to time.wallclock() (try to get the most accurate clock) but is not available if the system doesn't provide a monotonic clock. It may also fail at runtime if Python cannot find a monotonic clock, whereas time.clock() and time.wallclock() fallback on a wallclock which may go backward on NTP adjust.

The documentation of the patch should be improved :-)

wallclock() tests may be simplified or dropped because they may fail on NTP adjust.
Date User Action Args
2012-01-24 00:22:30vstinnersetrecipients: + vstinner, belopolsky
2012-01-24 00:22:29vstinnersetmessageid: <>
2012-01-24 00:22:29vstinnerlinkissue13846 messages
2012-01-24 00:22:28vstinnercreate