homepage

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 vstinner
Recipients nicholas.riley, vstinner
Date 2012年03月12日.23:36:19
SpamBayes Score 0.0008629451
Marked as misclassified No
Message-id <1331595380.72.0.717986946814.issue14277@psf.upfronthosting.co.za>
In-reply-to
Content
time.monotonic() has 3 implementations:
* Windows: QueryPerformanceCounter() with QueryPerformanceFrequency()
* Mac OS X: mach_absolute_time() with mach_timebase_info()
* UNIX: clock_gettime(CLOCK_MONOTONIC_RAW) or clock_gettime(CLOCK_MONOTONIC)
QueryPerformanceFrequency() returns the frequency "in counts per second" according to the doc.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms644905(v=vs.85).aspx
mach_absolute_time() with mach_timebase_info() returns a number of seconds, but Python uses *1e-9.
clock_gettime() uses a timespec structure and Python uses *1e-9.
It looks like to mention that time.monotonic() unit is seconds.
History
Date User Action Args
2012年03月12日 23:36:20vstinnersetrecipients: + vstinner, nicholas.riley
2012年03月12日 23:36:20vstinnersetmessageid: <1331595380.72.0.717986946814.issue14277@psf.upfronthosting.co.za>
2012年03月12日 23:36:20vstinnerlinkissue14277 messages
2012年03月12日 23:36:19vstinnercreate

AltStyle によって変換されたページ (->オリジナル) /