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

[STINNER Victor]

STINNER Victor added the comment:

The problem with pystone is that such tool is used to compare performances between different versions of Python. If pystone uses a different clock in Python 3.4, you may not be able to compare compare results with older Python versions.

In my opinion, such change should not be done before Python 3.5. 3.4 beta 3 has already been released.

----------
versions: +Python 3.5 -Python 3.3, Python 3.4

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