Marc-Andre Lemburg <m...@egenix.com> added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31803> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
