[issue14397] Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock
report at bugs.python.org
Sun Mar 25 12:24:28 CEST 2012
Marc-Andre Lemburg <mal at egenix.com> added the comment:
Yury Selivanov wrote:
> Yury Selivanov <yselivanov at gmail.com> added the comment:
>> A monotonic clock is not suitable for measuring durations, as it may still jump forward. A steady clock will not.
> Well, Victor's implementation of 'steady()' is just a tiny wrapper, which uses 'monotonic()' or 'time()' if the former is not available. Hence 'steady()' is a misleading name.
I think time.monotonic() is a better name.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list