Message304504
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:35 | benhoyt | set | recipients:
+ benhoyt, lemburg, fdrake, belopolsky, vstinner |
2017-10-17 13:26:35 | benhoyt | set | messageid: <1508246795.28.0.213398074469.issue31803@psf.upfronthosting.co.za> |
2017-10-17 13:26:35 | benhoyt | link | issue31803 messages |
2017-10-17 13:26:35 | benhoyt | create | |
|