[Python-checkins] peps: PEP 418: Move resolution and accuracy definitions to the Definition section

[victor.stinner]

http://hg.python.org/peps/rev/4b1dbc2d1f08
changeset:   4208:4b1dbc2d1f08
user:        Victor Stinner <victor.stinner at gmail.com>
date:        Mon Apr 09 13:04:15 2012 +0200
summary:
  PEP 418: Move resolution and accuracy definitions to the Definition section

files:
  pep-0418.txt |  27 +++++++++++++++++----------
  1 files changed, 17 insertions(+), 10 deletions(-)


diff --git a/pep-0418.txt b/pep-0418.txt
--- a/pep-0418.txt
+++ b/pep-0418.txt
@@ -214,6 +214,23 @@
 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 @@
 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:
 
 =========================  ================  ===============

-- 
Repository URL: http://hg.python.org/peps