Message304507
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:45 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, lemburg, fdrake, belopolsky, vstinner, benjamin.peterson, benhoyt |
2017-10-17 13:38:45 | serhiy.storchaka | set | messageid: <1508247525.12.0.213398074469.issue31803@psf.upfronthosting.co.za> |
2017-10-17 13:38:45 | serhiy.storchaka | link | issue31803 messages |
2017-10-17 13:38:45 | serhiy.storchaka | create | |
|