[TIP] Result protocol / problems being solved
sienkiew at stsci.edu
Tue Apr 14 09:31:34 PDT 2009
Scott David Daniels wrote:
> On Windows, time.clock() has higher precision than time.time()
> It returns ime in seconds (so is in some sense compatible), but uses a
> that doesn't get time adjustment the way the date & time-of-day do
> (time.time() has better synchronization with the atomic clock, but at
> the cost of local adjustments. If your timing interval covers one of those
> adjustments, the timing on that measurement will be mis-measured (and
> may even be negative).
Wait a minute --- the only way I can see that it could be negative is if
stop_time < start_time. Are you saying that time can actually run
_backwards_ on Windows?
More information about the testing-in-python