STINNER Victor <vstin...@python.org> added the comment:
Another way to understand the problem: nanosecond (int) => seconds (float) =>
nanoseconds (int) roundtrip looses precison.
>>> a=1580301619906185300
>>> a/1e9*1e9
1.5803016199061852e+18
>>> b=int(a/1e9*1e9)
>>> b
1580301619906185216
>>> a - b
84
The best would be to add a round parameter to _PyTime_AsSecondsDouble(), but
I'm not sure how to implement it.
The following rounding mode is used to read a clock:
/* Round towards minus infinity (-inf).
For example, used to read a clock. */
_PyTime_ROUND_FLOOR=0,
_PyTime_ROUND_FLOOR is used in time.clock_settime(), time.gmtime(),
time.localtime() and time.ctime() functions: to round input arguments.
time.time(), time.monotonic() and time.perf_counter() converts _PyTime_t to
float using _PyTime_AsSecondsDouble() (which currently has no round parameter)
for their output.
See also my rejected PEP 410 ;-)
--
One way to solve this issue is to document how to compare time.time() and
time.time_ns() timestamps in a reliable way.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue39484>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
