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 christian.heimes, python-dev, tim.peters, vstinner, zach.ware
Date 2013-12-23.21:32:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbv68rjV1t_XM-DZ+zSoccN+sVxsP3PytyiHRgQXezuNQ@mail.gmail.com>
In-reply-to <1387822668.29.0.83777920319.issue19999@psf.upfronthosting.co.za>
Content
For more info on time, you can refer to the PEP 418.

I may be interesting to add "sleep" to time.get_clock_info(). time.sleep()
uses WaitForSingleObject() on windows. It may use internally a different
clock with a different resolution than time.monoyonic (GetTickCount). The
PEP says "WaitForSingleObject(): use the same timer than GetTickCount()
with the same precision."

I don't think that it's very useful to investigate the rounding issue on
Windows. The resolution of Windows clocks is very coarse (15 ms, 10^-2)
compared to Unix clocks (usually a few nanoseconds, 10^-9)... I changed
recently the unit test to check if a sleep of 0.5 seconds gives a time
delta of at least 0.5 seconds. The minimum delta can be set to 0.45 sec
with a comment refering to this issue.
History
Date User Action Args
2013-12-23 21:32:43vstinnersetrecipients: + vstinner, tim.peters, christian.heimes, python-dev, zach.ware
2013-12-23 21:32:43vstinnerlinkissue19999 messages
2013-12-23 21:32:42vstinnercreate