Florent Xicluna <florent.xicl...@gmail.com> added the comment: Actually, I discovered "python -m test.pystone" during the talk of Mike Müller at EuroPython. http://is.gd/fasterpy
Even if they are suboptimal for true benchmarks, they should probably be mentioned somewhere. In the same paragraph, there should be a link to the "Grand Unified Python Benchmark Suite" as best practice: http://hg.python.org/benchmarks http://hg.python.org/benchmarks/file/tip http://hg.python.org/benchmarks/file/tip/README.txt The last paragraph of this wiki page might be reworded and included in the Python documentation: http://code.google.com/p/unladen-swallow/wiki/Benchmarks http://code.google.com/p/unladen-swallow/wiki/Benchmarks#Benchmarks_we_don't_use BTW, there's also this website which seems not updated anymore… http://speed.python.org/ ---------- nosy: +jnoller _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15369> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
