16 Oct
2017
16 Oct
'17
7:03 a.m.
On Mon, Oct 16, 2017 at 08:40:33AM +0200, Stephan Houben wrote:
"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 due to continental drift starts to matter?
tai64na has supported attoseconds for quite some time: https://cr.yp.to/libtai/tai64.html The relativity issue is declared to be out of scope for the document. :-) Stefan Krah