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 benhoyt
Recipients belopolsky, benhoyt, fdrake, lemburg, vstinner
Date 2017-10-17.13:26:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I don't think this is a good idea. I still use time.clock() out of habit (on Windows), and from the PR it's clear that the standard library and tests do too. I wouldn't be at all surprised to find others do as well.

I realize it's been deprecated since 3.3, but without a DeprecatingWarning, that's easy to miss. What about adding a DeprecatingWarning for 3.7 and deprecate it later, maybe in 3.9? (I know that's a long time, but time.clock() is an old function so we should be cautious!)
Date User Action Args
2017-10-17 13:26:35benhoytsetrecipients: + benhoyt, lemburg, fdrake, belopolsky, vstinner
2017-10-17 13:26:35benhoytsetmessageid: <>
2017-10-17 13:26:35benhoytlinkissue31803 messages
2017-10-17 13:26:35benhoytcreate