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 Jim.Jewett, docs@python, vstinner
Date 2012-03-19.12:21:52
SpamBayes Score 0.0007183663
Marked as misclassified No
Message-id <1332159713.49.0.838978482208.issue14318@psf.upfronthosting.co.za>
In-reply-to
Content
> Does "may not" mean that the user isn't allowed to adjust it,
> or that they system won't always have adjusted it?

It depends on which clock is used.

 - clock_gettime(CLOCK_MONOTONIC_RAW) cannot be adjusted
 - clock_gettime(CLOCK_MONOTONIC) can be adjusted by NTP (only its speed, no forward or backward jump)
 - I don't think that QueryPerformanceCounter() can be adjusted
 - gettimeofday(), ftime() and time() are the system clock and can be changed manually by the system administrator or automatically by NTP (maybe with a jump, forward or backward)
 - clock() is used on Windows if QueryPerformanceFrequency failed. I donk't know if it can be ajdusted

It is important to mention that time.steady() may be adjusted in some cases.
History
Date User Action Args
2012-03-19 12:21:53vstinnersetrecipients: + vstinner, docs@python, Jim.Jewett
2012-03-19 12:21:53vstinnersetmessageid: <1332159713.49.0.838978482208.issue14318@psf.upfronthosting.co.za>
2012-03-19 12:21:52vstinnerlinkissue14318 messages
2012-03-19 12:21:52vstinnercreate