Ken Healy added the comment:
Hi Terry,
I'm new to this so apologies in advance if this is a silly question...can you
explain why you removed 3.5 and 3.6 from the versions list? I have tested that
the issue is present in 3.6 and the offending code has been present since
time.perf_co
Ken Healy added the comment:
Note that this offset subtraction behavior appears to be inherited from
time.clock(), which did not make any guarantees about returning a system-wide
value:
https://github.com/python/cpython/commit/ec89539d6103665a7a5c7234cf09f27c1c72#diff
New submission from Ken Healy :
The documentation for time.perf_counter() indicates it should return a
system-wide value: https://docs.python.org/3/library/time.html#time.perf_counter
This is not true on Windows, as a process-specific offset is subtracted from
the underlying
