From 253f4b32a09c95676f6c0b81679c53654111bb12 Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Mon, 16 Oct 2017 18:51:38 +0200 Subject: [PATCH] PEP 564: leave "unchanged functions" question open --- pep-0564.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pep-0564.rst b/pep-0564.rst index fe7f31577..445d41e12 100644 --- a/pep-0564.rst +++ b/pep-0564.rst @@ -192,6 +192,9 @@ Example of unchanged functions: Since the ``time.clock()`` function was deprecated in Python 3.3, no ``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 =========================== @@ -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 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 -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 to support sub-nanosecond resolution.