[Python-Dev] this is why we shouldn't call it a "monotonic clock" (was: PEP 418 is too divisive and confusing and should be postponed)
Kristján Valur Jónsson
kristjan at ccpgames.com
Fri Apr 6 19:07:48 CEST 2012
This is the original reason for the original defect (issue 10278)
unix' clock() doesn't actually provide a clock in this sense, it provides a resource usage metric.
Frá: python-dev-bounces+kristjan=ccpgames.com at python.org [python-dev-bounces+kristjan=ccpgames.com at python.org] fyrir hönd Steven D'Aprano [steve at pearwood.info]
Sent: 6. apríl 2012 10:12
Efni: Re: [Python-Dev] this is why we shouldn't call it a "monotonic clock" (was: PEP 418 is too divisive and confusing and should be postponed)
I think that this is incorrect.
py> time.clock(); time.sleep(10); time.clock()
Python-Dev mailing list
Python-Dev at python.org
More information about the Python-Dev