Harro de Jong wrote: > Thanks for the pointer. I was using time.time(), which I now see isn't > very accurate on Windows. time.clock() is more accurate on Windows (and much less so on Linux, where it also measures something completely different.)