This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients belopolsky, benhoyt, benjamin.peterson, ethan.furman, fdrake, lemburg, mrabarnett, serhiy.storchaka, vstinner
Date 2017-10-26.20:27:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
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.

Date User Action Args
2017-10-26 20:27:30lemburgsetrecipients: + lemburg, fdrake, belopolsky, vstinner, benjamin.peterson, mrabarnett, benhoyt, ethan.furman, serhiy.storchaka
2017-10-26 20:27:30lemburglinkissue31803 messages
2017-10-26 20:27:30lemburgcreate