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 pfalcon
Recipients fdrake, pfalcon, vstinner, yselivanov
Date 2014-02-02.22:42:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391380969.25.0.613817641283.issue20475@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, and my note about "scientificity" above. Also compare with your own account of time.perf_counter() above ("Usually time.perf_counter() is the expected function.")

Also, I didn't want to start discussion on how to do benchmarking right, just to point out a small inconsistency, and suggest a fix which balances on (down-to-earth) correctness and practicality. It even can be ignored, except that such small inconsistencies accumulate and then some time later stick from every hole if not addressed.
History
Date User Action Args
2014-02-02 22:42:49pfalconsetrecipients: + pfalcon, fdrake, vstinner, yselivanov
2014-02-02 22:42:49pfalconsetmessageid: <1391380969.25.0.613817641283.issue20475@psf.upfronthosting.co.za>
2014-02-02 22:42:49pfalconlinkissue20475 messages
2014-02-02 22:42:49pfalconcreate