➜

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 pitrou
Recipients fdrake, pfalcon, pitrou, vstinner, yselivanov
Date 2014-02-03.00:12:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391386378.45.0.979168341839.issue20475@psf.upfronthosting.co.za>
In-reply-to
Content 
> If pystone uses a different clock in Python 3.4, you may not be able 
> to compare compare results with older Python versions.

This sounds a bit silly. Typical pystone runs last a couple seconds at most, there won't be a significant clock drift in such a short amount of time.

Besides, if time.clock() is deprecated, pystone will *have* to be modified one day, anyway.
History
Date User Action Args
2014-02-03 00:12:58pitrousetrecipients: + pitrou, fdrake, pfalcon, vstinner, yselivanov
2014-02-03 00:12:58pitrousetmessageid: <1391386378.45.0.979168341839.issue20475@psf.upfronthosting.co.za>
2014-02-03 00:12:58pitroulinkissue20475 messages
2014-02-03 00:12:58pitroucreate