time.clock() or Windows bug?
timr at probo.com
Wed Jun 11 08:05:03 CEST 2008
Nick Craig-Wood <nick at craig-wood.com> wrote:
>Hmmm, 10,000,000 cycles (40 ms @2.5GHz) is nowhere near the ~90,000
>second jump in time.clock() output reported by the OP. I wonder if
>there could be a different cause?
Just wild theorizing, but it's possible that they are actually getting a
negative delta, and some kind of signed/unsigned manipulation produces the
Tim Roberts, timr at probo.com
Providenza & Boekelheide, Inc.
More information about the Python-list