classification
Title: timeit CLI best of 3: undocumented output format
Type: enhancement Stage: needs patch
Components: Documentation Versions: Python 3.6, Python 3.5, Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, hachat, r.david.murray, rbcollins
Priority: normal Keywords: patch

Created on 2015-01-07 08:53 by hachat, last changed 2016-08-24 00:52 by r.david.murray.

Files
File name Uploaded Description Edit
issue-23183-1.patch rbcollins, 2015-03-17 21:25 review
Messages (3)
msg233570 - (view) Author: Chathuranga (hachat) Date: 2015-01-07 08:53
easy

Following command is executed in terminal to use timeit module to measure time.

python -m timeit -v -n 3 "time.sleep(1)"

Output of the command:
raw times: 3 3 3
3 loops, best of 3: 1 sec per loop

The interpretation of this output is unclear, and no details available in the documentation.
https://docs.python.org/2/library/timeit.html#command-line-interface
msg238340 - (view) Author: Robert Collins (rbcollins) * (Python committer) Date: 2015-03-17 21:25
Here is a patch with some prose - feedback appreciated!
msg273526 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2016-08-24 00:52
I think the use of "timing loop" is very confusing, since the word 'loop' refers to one execution of the statement body in the actual output text.  What about calling it a 'timing run'?
 
It looks like whatever we come up with should be applied to 3.5 and 3.6 as well.
History
Date User Action Args
2016-08-24 00:52:30r.david.murraysetversions: + Python 3.5, Python 3.6
nosy: + r.david.murray

messages: + msg273526

stage: commit review -> needs patch
2015-08-26 00:42:15rbcollinssetstage: patch review -> commit review
2015-03-17 21:25:40rbcollinssetstage: patch review
2015-03-17 21:25:27rbcollinssetfiles: + issue-23183-1.patch
keywords: + patch
messages: + msg238340
2015-03-17 21:24:45rbcollinssetnosy: + rbcollins
2015-01-07 08:53:19hachatcreate