[Python-ideas] Add time.time_ns(): system clock with nanosecond resolution
Victor Stinner
victor.stinner at gmail.com
Fri Oct 20 16:29:14 EDT 2017
More information about the Python-ideas mailing list
Fri Oct 20 16:29:14 EDT 2017
- Previous message (by thread): [Python-ideas] Add time.time_ns(): system clock with nanosecond resolution
- Next message (by thread): [Python-ideas] (PEP 555 subtopic) Propagation of context in async code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi francis, Le 20 oct. 2017 18:42, "francismb" <francismb at email.de> a écrit : Hi Victor, On 10/13/2017 04:12 PM, Victor Stinner wrote: > I would like to add: > > * time.time_ns() > * time.monotonic_ns() > * time.perf_counter_ns() > * time.clock_gettime_ns() > * time.clock_settime_ns() due nano vs. pico vs. ... why not something like (please change '_in' for what you like): time.time_in(precision) time.monotonic_in(precision) If you are not aware yet, I wrote a full PEP: PEP 564. The two discussed idea are alreafy listed in the PEP, configurable precision and sub-nanosecond resolution. I tried to explain why I proposed time.time_ns() in detail in the PEP: https://www.python.org/dev/peps/pep-0564/#sub-nanosecond-resolution You may want to join the discussion on python-dev. Victor -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-ideas/attachments/20171020/c164a868/attachment.html>
- Previous message (by thread): [Python-ideas] Add time.time_ns(): system clock with nanosecond resolution
- Next message (by thread): [Python-ideas] (PEP 555 subtopic) Propagation of context in async code
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list