Marc-Andre Lemburg <m...@egenix.com> added the comment: On 26.10.2017 13:46, Serhiy Storchaka wrote: > > It is very bad, that the function with such attractive name has different > meaning on Windows and Unix. I'm sure that virtually all uses of clock() are > broken because its behavior on other platform than used by the author of the > code.
Not really, no. People who write cross-platform code are well aware of the differences of time.clock() and people who just write for one platform know how the libc function of the same function works on their platform. Unix: http://man7.org/linux/man-pages/man3/clock.3.html Windows: https://msdn.microsoft.com/en-us/library/4e2ess30.aspx ---------- _______________________________________ 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
