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 serhiy.storchaka
Recipients belopolsky, benhoyt, benjamin.peterson, fdrake, lemburg, serhiy.storchaka, vstinner
Date 2017-10-17.13:38:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A runtime deprecation warning was not emitted in 3.3 because two alternatives, time.process_time() and time.perf_counter(), were not available before 3.3. It would be hard to write a warning-free code that supports 3.3 and earlier versions at the same time. But now 3.2 is virtually out of use and I think we can start emitting a deprecation warning at runtime.

And maybe make 2to3 replacing time.clock() with time.process_time() or time.perf_counter()?
Date User Action Args
2017-10-17 13:38:45serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, fdrake, belopolsky, vstinner, benjamin.peterson, benhoyt
2017-10-17 13:38:45serhiy.storchakasetmessageid: <>
2017-10-17 13:38:45serhiy.storchakalinkissue31803 messages
2017-10-17 13:38:45serhiy.storchakacreate