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

PEP 564: leave "unchanged functions" question open

This commit is contained in:
Victor Stinner 2017-10-16 18:51:38 +02:00
parent 04a2339ff7
commit 253f4b32a0
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
pep-0564.rst
View File

@ -192,6 +192,9 @@ Example of unchanged functions:
Since the ``time.clock()`` function was deprecated in Python 3.3, no Since the ``time.clock()`` function was deprecated in Python 3.3, no
``time.clock_ns()`` is added. ``time.clock_ns()`` is added.
New nanosecond flavor of these functions may be added later, if a
concrete use case comes in.
Alternatives and discussion Alternatives and discussion
=========================== ===========================
@ -209,7 +212,7 @@ Hardware clock with a resolution better than 1 nanosecond already
exists. For example, the frequency of a CPU TSC clock is the CPU base exists. For example, the frequency of a CPU TSC clock is the CPU base
frequency: the resolution is around 0.3 ns for a CPU running at 3 frequency: the resolution is around 0.3 ns for a CPU running at 3
GHz. Users who have access to such hardware and really need GHz. Users who have access to such hardware and really need
sub-nanosecond resolution can easyly extend Python for their needs. sub-nanosecond resolution can easily extend Python for their needs.
Such rare use case don't justify to design the Python standard library Such rare use case don't justify to design the Python standard library
to support sub-nanosecond resolution. to support sub-nanosecond resolution.