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 steven.daprano
Recipients dmoore, ezio.melotti, georg.brandl, giampaolo.rodola, gvanrossum, ncoghlan, rhettinger, steven.daprano, tim.peters
Date 2014-06-16.02:55:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20140616025518.GE7742@ando>
In-reply-to <1402884562.62.0.868752551624.issue19495@psf.upfronthosting.co.za>
Content
On Mon, Jun 16, 2014 at 02:09:22AM +0000, Raymond Hettinger wrote:

> Perhaps a time-elapsed context manager would be a better fit in the 
> contextlib module (which contains more general purpose macro-level 
> tools usable for many different tasks) rather than the timeit module 
> (which is more narrowly tailored to high-quality reproducable in-vitro 
> performance analysis at a fine-grained level).

Perhaps you're right, but "timeit" is a fairly broad description, and I 
would expect anything related to the task "time it" to be found there. 
I'm +0.9 on timeit and +0.4 on contextlib.

Does anyone else have an opinion on where this belongs?
History
Date User Action Args
2014-06-16 02:55:24steven.dapranosetrecipients: + steven.daprano, gvanrossum, tim.peters, georg.brandl, rhettinger, ncoghlan, giampaolo.rodola, ezio.melotti, dmoore
2014-06-16 02:55:24steven.dapranolinkissue19495 messages
2014-06-16 02:55:24steven.dapranocreate