report at bugs
Jul 7, 2008, 6:43 PM
Post #1 of 2
(81 views)
Permalink
|
|
[issue3318] Documentation: timeit: "lower bound" should read "upper bound"
|
|
New submission from unutbu <driabslg[at]yahoo.com>:
Re: http://docs.python.org/lib/module-timeit.html
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.
----------
assignee: georg.brandl
components: Documentation
messages: 69405
nosy: georg.brandl, unutbu
severity: normal
status: open
title: Documentation: timeit: "lower bound" should read "upper bound"
versions: Python 2.5
_______________________________________
Python tracker <report[at]bugs.python.org>
<http://bugs.python.org/issue3318>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|
