[docs] Use full names for time units (GH-28611)

Use "second", "millisecond", "microsecond", "nanosecond" instead of
"sec", "ms", "msec", "us", "ns", etc.
This commit is contained in:
Serhiy Storchaka 2021-09-29 12:09:56 +03:00 committed by GitHub
parent e046aabbe3
commit 233b9da07d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
13 changed files with 21 additions and 20 deletions

View file

@ -243,14 +243,14 @@ time
----
* On Unix, :func:`time.sleep` now uses the ``clock_nanosleep()`` or
``nanosleep()`` function, if available, which has a resolution of 1 ns
(10\ :sup:`-9` sec), rather than using ``select()`` which has a resolution
of 1 us (10\ :sup:`-6` sec).
``nanosleep()`` function, if available, which has a resolution of 1 nanosecond
(10\ :sup:`-9` seconds), rather than using ``select()`` which has a resolution
of 1 microsecond (10\ :sup:`-6` seconds).
(Contributed by Livius and Victor Stinner in :issue:`21302`.)
* On Windows, :func:`time.sleep` now uses a waitable timer which has a
resolution of 100 ns (10\ :sup:`-7` sec). Previously, it had a solution of 1 ms
(10\ :sup:`-3` sec).
resolution of 100 nanoseconds (10\ :sup:`-7` seconds). Previously, it had
a resolution of 1 millisecond (10\ :sup:`-3` seconds).
(Contributed by Livius and Victor Stinner in :issue:`21302`.)
unicodedata

View file

@ -671,7 +671,7 @@ time
On AIX, :func:`~time.thread_time` is now implemented with ``thread_cputime()``
which has nanosecond resolution, rather than
``clock_gettime(CLOCK_THREAD_CPUTIME_ID)`` which has a resolution of 10 ms.
``clock_gettime(CLOCK_THREAD_CPUTIME_ID)`` which has a resolution of 10 milliseconds.
(Contributed by Batuhan Taskaya in :issue:`40192`)
sys