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 r.david.murray
Recipients THRlWiTi, cheryl.sabella, dmoore, ezio.melotti, georg.brandl, giampaolo.rodola, martin.panter, ncoghlan, r.david.murray, rbcollins, rhettinger, steven.daprano, tim.peters
Date 2018-01-30.20:06:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1517342811.79.0.467229070634.issue19495@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, we just ran in to the need for this on our project, and used 'Time' from the contexttimer package on pypi.  In our use case we want the number so we can log it, and what we care about is the actual elapsed time, not a precise measurement of the code block, because it for system monitoring and metrics, not hardcore performance analysis.  

Having this always print would indeed be sub-optimal :)
History
Date User Action Args
2018-01-30 20:06:51r.david.murraysetrecipients: + r.david.murray, tim.peters, georg.brandl, rhettinger, ncoghlan, giampaolo.rodola, rbcollins, ezio.melotti, steven.daprano, THRlWiTi, martin.panter, dmoore, cheryl.sabella
2018-01-30 20:06:51r.david.murraysetmessageid: <1517342811.79.0.467229070634.issue19495@psf.upfronthosting.co.za>
2018-01-30 20:06:51r.david.murraylinkissue19495 messages
2018-01-30 20:06:51r.david.murraycreate