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 serhiy.storchaka
Recipients belopolsky, benhoyt, benjamin.peterson, ethan.furman, fdrake, lemburg, mrabarnett, serhiy.storchaka, vstinner
Date 2017-10-26.11:46:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1509018364.77.0.213398074469.issue31803@psf.upfronthosting.co.za>
In-reply-to
Content
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. Adding a DeprecationWarning and finally removing it looks right thing to me. But we should keep it while 2.7 and versions older than 3.3 are in use.
History
Date User Action Args
2017-10-26 11:46:04serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, fdrake, belopolsky, vstinner, benjamin.peterson, mrabarnett, benhoyt, ethan.furman
2017-10-26 11:46:04serhiy.storchakasetmessageid: <1509018364.77.0.213398074469.issue31803@psf.upfronthosting.co.za>
2017-10-26 11:46:04serhiy.storchakalinkissue31803 messages
2017-10-26 11:46:04serhiy.storchakacreate