Mark Lawrence added the comment:
Is there anything else that can be done or needs doing here?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20101
___
STINNER Victor added the comment:
time.sleep() and time.monotonic() don't use the same clock. Python cannot fix
Windows clocks, it's not a bug.
--
resolution: - not a bug
status: open - closed
___
Python tracker rep...@bugs.python.org
Martin v. Löwis added the comment:
As a further datapoint, it would be good to find out whether any of you has NTP
enabled, and if so, against what time server. To find out, open the clock
settings (Datums- und Uhrzeiteinstellungen ändern), and go to NTP tab
(Internetzeit).
--
nosy:
STINNER Victor added the comment:
time.get_clock_info(time) and time.get_clock_info(monotonic) is currently
using GetSystemTimeAdjustment(). In msg206886 it was said that
GetSystemTimeAdjustment is not the function to look at.
Should we modify this function to use NtQueryTimerResolution()
Zachary Ware added the comment:
Martin v. Löwis wrote:
As a further datapoint, it would be good to find out whether any of you has
NTP enabled, and if so, against what time server. To find out, open the clock
settings (Datums- und Uhrzeiteinstellungen ändern), and go to NTP tab
Roundup Robot added the comment:
New changeset 82df66a091da by Zachary Ware in branch '3.3':
Issue #20101: Allow test_monotonic to pass on Windows machines on which
http://hg.python.org/cpython/rev/82df66a091da
New changeset e2a1400b7db9 by Zachary Ware in branch 'default':
Issue #20101: Merge
Tim Peters added the comment:
1. I'm sync'ing with north-america.pool.ntp.org. But the docs on my box say
Your clock is typically updated once a week, and I believe it.
2. I just ran Zach's program again, with the same Python, and _this_ time
'time' passed 25 times (as did 'monotonic').
Zachary Ware added the comment:
I ran the same test on all of the Windows buildbots, with the following results:
x86 XP-4:
http://buildbot.python.org/all/builders/x86%20XP-4%20custom/builds/33/steps/test/logs/stdio
monotonic: good
time: good
clock/perf_counter: 10 failures
x86 Windows7
Changes by Jeremy Kloth jeremy.kloth+python-trac...@gmail.com:
--
nosy: +jkloth
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20101
___
___
Tim Peters added the comment:
I'm not sanguine about fixing any of this :-( The Microsoft docs are awful,
and the more web searches I do the more I realize that absolutely everyone is
confused, just taking their best guesses.
FYI, here are results from your new program on my 32-bit Vista
New submission from Zachary Ware:
For previous discussion, see issue1.
To summarize, time on Windows is far from straight-forward, and currently for
t1 = time.monotonic()
time.sleep(0.5)
t2 = time.monotonic()
dt = t2-t1
dt may end up as very slightly smaller than 0.5 (0.499003017485
11 matches
Mail list logo
