[Python-ideas] Why not picoseconds?

Stefan Krah stefan at bytereef.org
Mon Oct 16 03:03:14 EDT 2017

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:


The relativity issue is declared to be out of scope for the document. :-)

Stefan Krah

More information about the Python-ideas mailing list