[issue20475] pystone.py in 3.4 still uses time.clock(), even though it's marked as deprecated since 3.3

[Antoine Pitrou]

Antoine Pitrou added the comment:

Paul:

> 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)

pybench is so synthetic it's almost a nano-benchmark. I would suggest using the benchmarks suite, which will give more useful numbers IMHO:
http://hg.python.org/benchmarks/

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20475>
_______________________________________