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 docs@python, hachat, r.david.murray, rbcollins
Date 2016-08-24.00:52:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471999950.18.0.247130941779.issue23183@psf.upfronthosting.co.za>
In-reply-to
Content
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.murraysetrecipients: + r.david.murray, rbcollins, docs@python, hachat
2016-08-24 00:52:30r.david.murraysetmessageid: <1471999950.18.0.247130941779.issue23183@psf.upfronthosting.co.za>
2016-08-24 00:52:30r.david.murraylinkissue23183 messages
2016-08-24 00:52:29r.david.murraycreate