[Python-ideas] Why not picoseconds?

Stephan Houben stephanh42 at gmail.com
Mon Oct 16 02:40:33 EDT 2017

2017-10-15 22:08 GMT+02:00 Eric V. Smith <eric at trueblade.com>:
>From Victor's original message, describing the current functions using
64-bit binary floating point numbers (aka double). They lose precision:

"The problem is that Python returns time as a floatting point number
> which is usually a 64-bit binary floatting number (in the IEEE 754
> format). This type starts to loose nanoseconds after 104 days."
Do we realize that at this level of accuracy, relativistic time dilatation
to continental drift starts to matter?


> Eric.
> _______________________________________________
> Python-ideas mailing list
> Python-ideas at python.org
> https://mail.python.org/mailman/listinfo/python-ideas
> Code of Conduct: http://python.org/psf/codeofconduct/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20171016/a237ceac/attachment.html>

More information about the Python-ideas mailing list