Paul Sokolovsky added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20475> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com