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:28:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The problem with pystone is that such tool is used to compare performances between different versions of Python.

That's why I just propose to switch it to time.time(), which surely is available on each and every Python version and implementation. If there's a concern that some implementation may have only 1-second precision, then: 1) well, pystone has limits to its "scientificity", it's more like quick-run-anywhere, there's pybench for "real" testing (it's maintained and supported I hope); 2) number of iteratations can be bumped from 50K to 200K-500K.
Date User Action Args
2014-02-02 22:28:06pfalconsetrecipients: + pfalcon, fdrake, vstinner, yselivanov
2014-02-02 22:28:06pfalconsetmessageid: <>
2014-02-02 22:28:06pfalconlinkissue20475 messages
2014-02-02 22:28:06pfalconcreate