Specify time unit for timeit CLI

[serhiy-storchaka]

BPO	18983
Nosy	@tim-one, @birkenfeld, @pitrou, @rbtcollins, @ezio-melotti, @berkerpeksag, @serhiy-storchaka, @vajrasky, @jstasiak, @pquentin
Files	issue18983.patch issue18983.patch issue18983_v2.patch issue18983_v3.patch issue18983_v4.patch issue18983_v5.patch issue18983_v5.patch issue18983_v6.patch

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2015-03-17.21:01:41.998>
created_at = <Date 2013-09-08.21:15:56.832>
labels = ['easy', 'type-feature', 'library']
title = 'Specify time unit for timeit CLI'
updated_at = <Date 2015-03-17.21:01:41.997>
user = 'https://github.com/serhiy-storchaka'

bugs.python.org fields:

activity = <Date 2015-03-17.21:01:41.997>
actor = 'rbcollins'
assignee = 'none'
closed = True
closed_date = <Date 2015-03-17.21:01:41.998>
closer = 'rbcollins'
components = ['Library (Lib)']
creation = <Date 2013-09-08.21:15:56.832>
creator = 'serhiy.storchaka'
dependencies = []
files = ['32862', '32874', '33058', '33064', '33066', '33067', '33068', '33095']
hgrepos = []
issue_num = 18983
keywords = ['patch', 'easy']
message_count = 27.0
messages = ['197322', '197333', '197345', '204541', '204606', '205612', '205697', '205720', '205723', '205731', '205736', '205737', '205738', '205914', '205922', '205923', '205931', '206834', '206869', '207990', '207995', '216024', '226093', '233346', '233348', '238337', '238338']
nosy_count = 13.0
nosy_names = ['tim.peters', 'georg.brandl', 'pitrou', 'rbcollins', 'ezio.melotti', 'python-dev', 'berker.peksag', 'serhiy.storchaka', 'Vincentdavis', 'vajrasky', 'jstasiak', 'Julian.Gindi', 'Quentin.Pradet']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue18983'
versions = ['Python 3.5']

[serhiy-storchaka]

Just an idea. Currently the timeit module in command line automatically choice most appropriate time unit for human readable output. But this makes the output less machine readable. I propose to add new option which specifies fixed time unit (usec, msec, sec).

[pitrou]

If you want the output to be machine readable, better go the full way and add a --json option, IMO.

[jstasiak]

My 2 cents - I'd split timeit.main function into processing part and argument parsing + data printing part so that you could use Python to call the first one to get the actual results (timings, numbers of loops etc.) and then present the data to the outside world in any needed format - no text parsing needed.

[JulianGindi]

I created a patch that allows users to specify a time unit output using the "-u" flag. Example usage:

python -m timeit -u "msec" '"-".join(str(n) for n in range(100))'

> 10000 loops, best of 3: 0.156 msec per loop

python -m timeit -u "sec" '"-".join(str(n) for n in range(100))'

> 10000 loops, best of 3: 0.000159 sec per loop

You can specify msec, sec, or usec. I am also interested in having a JSON option as mentioned by Antoine. Any thoughts?

[JulianGindi]

Updated patch to include unit tests.

[JulianGindi]

Just wanted to check to see if there was anything else I should do regarding this issue.

[JulianGindi]

Implemented proposed changes to patch. Simplified "for-loop" and implemented invalid input test.

[JulianGindi]

Incorporated updates suggested by serhiy.storchaka

[serhiy-storchaka]

It will be better to write error message to sys.stderr (see test_main_exception).

[JulianGindi]

Updated patch to log to stderr.

[JulianGindi]

Added newline after error message.

[serhiy-storchaka]

The patch is doubled.