[issue6061] time.clock(): overflow in programs that run for very long

Thomas Reiter added the comment: That version of Python is linked against 32-bit libc. Point of overflow corresponds to 2^31 us. -- status: open -> closed ___ Python tracker ___

[issue6061] time.clock(): overflow in programs that run for very long

Antoine Pitrou added the comment: It is very likely you have a 32-bit Python build because: >>> 2**32/100. 4294.967295998 and 4294 is exactly the number of seconds by which your clock() value wraps around. -- ___ Python tracker

[issue6061] time.clock(): overflow in programs that run for very long

Antoine Pitrou added the comment: time.clock() is a simple wrapper around the C stdlib clock() function. As the clock() man page says: « Note that the time can wrap around. On a 32-bit system where CLOCKS_PER_SEC equals 100 this function will return the same value approximately every 72 mi

[issue6061] time.clock(): overflow in programs that run for very long

New submission from Thomas Reiter : On a 64-bit Linux machine the attached program generates the following (shortened) output: $ python bug.py ... after 2145.49s: after 2145.82s: after 2146.14s: after 2146.47s: after 2146.80s: after 2147.13s: after 2147.45s: after -2147.19s: Here's your