diff options
| author | Martin v. Löwis <martin@v.loewis.de> | 2003-09-20 11:09:28 (GMT) |
|---|---|---|
| committer | Martin v. Löwis <martin@v.loewis.de> | 2003-09-20 11:09:28 (GMT) |
| commit | 7bdc484c97eb418dcffcdc7a4390e30818d277cb (patch) | |
| tree | cc19e790a6c12c8976e6ab18c13d18cdd6681ffd /Lib | |
| parent | 8f81c93b8c1b5aecf94a89c22d9f74eeb228a277 (diff) | |
| download | cpython-7bdc484c97eb418dcffcdc7a4390e30818d277cb.zip cpython-7bdc484c97eb418dcffcdc7a4390e30818d277cb.tar.gz cpython-7bdc484c97eb418dcffcdc7a4390e30818d277cb.tar.bz2 | |
Patch #808362: Fix typos.
Diffstat (limited to 'Lib')
| -rw-r--r-- | Lib/timeit.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/timeit.py b/Lib/timeit.py index d7a3a3d..1127aaa 100644 --- a/Lib/timeit.py +++ b/Lib/timeit.py @@ -33,7 +33,7 @@ The difference in default timer function is because on Windows, clock() has microsecond granularity but time()'s granularity is 1/60th of a second; on Unix, clock() has 1/100th of a second granularity and time() is much more precise. On either platform, the default timer -functions measures wall clock time, not the CPU time. This means that +functions measure wall clock time, not the CPU time. This means that other processes running on the same computer may interfere with the timing. The best thing to do when accurate timing is necessary is to repeat the timing a few times and use the best time. The -r option is |