Message 304567 - Python tracker

➜

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-18.09:09:00
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1508317740.52.0.213398074469.issue31803@psf.upfronthosting.co.za>
In-reply-to

Content
Initially the time module was a thin wrapper around C and OS time-related functions. It may be confusing that the behavior of time.clock() differs from the behavior of C's clock(). The documentation for clock() on MSDN suggests to use GetProcessTimes() for the behavior conforming the C standard. https://msdn.microsoft.com/en-us/library/4e2ess30.aspx

Initially the time module was a thin wrapper around C and OS time-related functions. It may be confusing that the behavior of time.clock() differs from the behavior of C's clock().

The documentation for clock() on MSDN suggests to use GetProcessTimes() for the behavior conforming the C standard.

https://msdn.microsoft.com/en-us/library/4e2ess30.aspx

History
Date	User	Action	Args
2017-10-18 09:09:00	serhiy.storchaka	set	recipients: + serhiy.storchaka, lemburg, fdrake, belopolsky, vstinner, benjamin.peterson, mrabarnett, benhoyt, ethan.furman
2017-10-18 09:09:00	serhiy.storchaka	set	messageid: <1508317740.52.0.213398074469.issue31803@psf.upfronthosting.co.za>
2017-10-18 09:09:00	serhiy.storchaka	link	issue31803 messages
2017-10-18 09:09:00	serhiy.storchaka	create