time.clock() going backwards??

Michiel Sikma michiel at thingmajig.org
Fri Aug 25 12:21:10 EDT 2006


Op 25-aug-2006, om 16:13 heeft Giovanni Bajo het volgende geschreven:

> Hello,
>
> Is it possible this to be a bug in Python itself
> (maybe, shooting at the moon, in the conversion between the 64bit  
> performance
> counter and the floating point representation returned by time.clock 
> ()), or
> could it be a bug in Windows itself or the mother board drivers  
> (buf if so,
> wouldn't other application start going mad)?
> -- 
> Giovanni Bajo

Very interesting! While I couldn't possibly know the answer to this,  
I do wonder which version of Python you were using. Is it the  
bleeding edge 2.5 release candidate?

Michiel




More information about the Python-list mailing list