homepage

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 jmetz
Recipients eli.bendersky, jmetz, ncoghlan, pitrou, rhettinger, ssapin
Date 2018年03月14日.14:18:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521037138.66.0.467229070634.issue5441@psf.upfronthosting.co.za>
In-reply-to
Content
Don't understand how #6422 addresses this - would also like to see a more convenient API for timing; at present CLI gives a nice formatted output, and timeit.timeit gives just the raw timing in seconds. 
Would be easy to implement by simply refactoring main() in to the command line parsing component (first ~ 50 lines from https://github.com/python/cpython/blob/master/Lib/timeit.py#L256 to ~https://github.com/python/cpython/blob/master/Lib/timeit.py#L312 ) and actual timing and printing component, which could then be called via API. 
Am happy to work this up if this can be reopened...?
History
Date User Action Args
2018年03月14日 14:18:58jmetzsetrecipients: + jmetz, rhettinger, ncoghlan, pitrou, eli.bendersky, ssapin
2018年03月14日 14:18:58jmetzsetmessageid: <1521037138.66.0.467229070634.issue5441@psf.upfronthosting.co.za>
2018年03月14日 14:18:58jmetzlinkissue5441 messages
2018年03月14日 14:18:58jmetzcreate

AltStyle によって変換されたページ (->オリジナル) /