Author lemburg
Recipients belopolsky, benhoyt, benjamin.peterson, ethan.furman, fdrake, lemburg, mrabarnett, serhiy.storchaka, vstinner
Date 2017-10-22.12:39:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <cf2bb815-fe6c-dbad-7b90-3b188f4415ee@egenix.com>
In-reply-to <1508521608.25.0.213398074469.issue31803@psf.upfronthosting.co.za>
Content
On 20.10.2017 19:46, Serhiy Storchaka wrote:
> 
> This will break a code that depends on the current behavior on non-Windows platforms. And this will contradict the expectation of non-Windows programmers. If change the behavior of clock() on non-Windows platforms, it should be done only after the period of emitting FutureWarning.

Could you explain which behavior is changed by this on non-Windows
platforms ?

time.clock() only switches to a more accurate clock. That's pretty
much it. Which clock it used on which platform was platform
dependent anyway, so there's no real change in behavior.

For benchmarking and other measurements, time.time() was recommended
on Unix and time.clock() on Windows. time.clock() never good
resolution on Unix, so the situation only improves by using
a more accurate clock.
History
Date User Action Args
2017-10-22 12:39:09lemburgsetrecipients: + lemburg, fdrake, belopolsky, vstinner, benjamin.peterson, mrabarnett, benhoyt, ethan.furman, serhiy.storchaka
2017-10-22 12:39:09lemburglinkissue31803 messages
2017-10-22 12:39:08lemburgcreate