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 vstinner
Recipients docs@python, flox, lemburg, pitrou, python-dev, vstinner
Date 2016-10-18.15:00:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476802816.36.0.414219269379.issue15369@psf.upfronthosting.co.za>
In-reply-to
Content
I'm closing the issue again.

Again, pybench moved to http://github.com/python/performance : please continue the discussion there if you consider that we still need to do something on pybench.

FYI I reworked deeply pybench recently using the new perf 0.8 API. perf 0.8 now supports running multiple benchmarks per script, so pybench was written as only a benchmark runner. Comparison between benchmarks can be done using performance, or directly using perf (python3 -m perf compare a.json b.json).
History
Date User Action Args
2016-10-18 15:00:16vstinnersetrecipients: + vstinner, lemburg, pitrou, flox, docs@python, python-dev
2016-10-18 15:00:16vstinnersetmessageid: <1476802816.36.0.414219269379.issue15369@psf.upfronthosting.co.za>
2016-10-18 15:00:16vstinnerlinkissue15369 messages
2016-10-18 15:00:16vstinnercreate