[Python-ideas] Why not picoseconds?
Thomas Jollans
tjol at tjol.eu
Mon Oct 16 11:46:53 EDT 2017
More information about the Python-ideas mailing list
Mon Oct 16 11:46:53 EDT 2017
- Previous message (by thread): [Python-ideas] Why not picoseconds?
- Next message (by thread): [Python-ideas] Why not picoseconds?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2017-10-16 16:42, MRAB wrote: > On 2017-10-16 13:30, Greg Ewing wrote: >> 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. >> > Is that an African or a European swallow? It starts African, but it flips and can be observed as either African or European in London. It's a neutrino swallow. -- Thomas Jollans
- Previous message (by thread): [Python-ideas] Why not picoseconds?
- Next message (by thread): [Python-ideas] Why not picoseconds?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-ideas mailing list