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 belopolsky
Recipients belopolsky, benhoyt, benjamin.peterson, ethan.furman, fdrake, lemburg, mrabarnett, serhiy.storchaka, vstinner
Date 2017-10-25.17:07:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I would like to add my voice to MAL's objections.  I was not aware of time.clock() depreciation before Victor brought this issue to my attention.  time.clock() is a very well-known API eponymous to a venerable UNIX system call.  Its limitations and platform dependencies are very well-known as well.  For someone new to python, seeing time.clock() would probably not require a trip to the library reference, but seeing time.perf_counter() is likely to cause a WTF reaction even from an experienced python developer.
Date User Action Args
2017-10-25 17:07:15belopolskysetrecipients: + belopolsky, lemburg, fdrake, vstinner, benjamin.peterson, mrabarnett, benhoyt, ethan.furman, serhiy.storchaka
2017-10-25 17:07:15belopolskysetmessageid: <>
2017-10-25 17:07:15belopolskylinkissue31803 messages
2017-10-25 17:07:15belopolskycreate