[Python-ideas] Why not picoseconds?

Greg Ewing greg.ewing at canterbury.ac.nz
Mon Oct 16 08:30:41 EDT 2017

Stephan Houben wrote:

> Interestingly, that 2.2e-16 pretty much aligns with the accuracy of the
> cesium atomic clocks which are currently used to *define* the second.
> So we move to this new API, we should provide our own definition
> of the second, since those rough SI seconds are just too imprecise for that.

The Python second: 1.1544865564196655e-06 of the time
taken for an unladen swallow to fly from Cape Town
to London.


More information about the Python-ideas mailing list