This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | unutbu |
|---|---|
| Recipients | georg.brandl, unutbu |
| Date | 2008年07月08日.01:43:09 |
| SpamBayes Score | 0.013478808 |
| Marked as misclassified | No |
| Message-id | <1215481393.4.0.322080093727.issue3318@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月08日 01:43:13 | unutbu | set | spambayes_score: 0.0134788 -> 0.013478808 recipients: + unutbu, georg.brandl |
| 2008年07月08日 01:43:13 | unutbu | set | spambayes_score: 0.0134788 -> 0.0134788 messageid: <1215481393.4.0.322080093727.issue3318@psf.upfronthosting.co.za> |
| 2008年07月08日 01:43:12 | unutbu | link | issue3318 messages |
| 2008年07月08日 01:43:10 | unutbu | create | |