[New-bugs-announce] [issue3318] Documentation: timeit: "lower bound" should read "upper bound"
report at bugs.python.org
Tue Jul 8 03:43:13 CEST 2008
New submission from unutbu <driabslg at yahoo.com>:
Where the documentation says "In a typical case, the lowest value gives
a lower bound for how fast your machine can run the given code snippet",
it should read instead,
"In a typical case, the lowest value gives an upper bound for how fast
your machine can run the given code snippet".
Clearly, if a machine can run a code snippet in x seconds with
background processes, then the fastest the machine can run the code
snippet (without background processes) should be <= x seconds. Therefore
x is an upper bound rather than a lower bound.
nosy: georg.brandl, unutbu
title: Documentation: timeit: "lower bound" should read "upper bound"
versions: Python 2.5
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce