iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 418: Move resolution and accuracy definitions to the Definition section

This commit is contained in:
Victor Stinner 2012-04-09 13:04:15 +02:00
parent 471e1412ec
commit 94d094d791
1 changed files with 17 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
pep-0418.txt
View File

@ -214,6 +214,23 @@ Return a dictionary with the following keys:
Definitions
===========
Resolution
----------
The resolution is the smallest difference between two timestamps supported by
the format used by the clock. For example, clock_gettime() uses a timespec
structure which has two integer fields, tv_sec and tv_nsec, so the resolution
is 1 nanosecond.
Accuracy
--------
The accuracy is the effective smallest difference of two timestamps of the
clock. It does not reflect the stability the clock rate. For example,
QueryPerformanceCounter() has a good accuracy but is known to not have a steady
rate.
Monotonic
---------
@ -301,16 +318,6 @@ GetTickCount[64]() 1 ms No Include suspend time
timeGetTime() 1 ms No ?
========================= =============== ================ ====================
The resolution is the smallest difference between two timestamps
supported by the format used by the clock. For example,
clock_gettime() uses a timespec structure which has two integer
fields, tv_sec and tv_nsec, so the resolution is 1 nanosecond.
The accuracy is the effective smallest difference of two timestamps of
the clock. It does not reflect the stability the clock rate. For
example, QueryPerformanceCounter() has a good accuracy but is known to
not have a steady rate.
Examples of clock accuracy on x86_64:
========================= ================ ===============