On 4/27/05, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Travis Watkins wrote:
>
> > Never trust the program you're running to give you accurate time. Use
> > 'time python foo.py' instead.
>
> so you can make sure that the thing you're measuring is hidden by all the
> irrelevant
> stuff that's goi
Travis Watkins wrote:
> Never trust the program you're running to give you accurate time. Use
> 'time python foo.py' instead.
so you can make sure that the thing you're measuring is hidden by all the
irrelevant
stuff that's going on when a process starts, and, if the thing you're measuring
is s
Travis Watkins wrote:
Never trust the program you're running to give you accurate time.
I thought (and think) that the measurements are sufficiently accurate, and the
differences sufficiently marked to support the speed claim. I also ran the test
with much longer cycles, checked the reported ti
