Ethan Furman <ethan at stoneleaf.us>: > On 12/11/2014 11:14 AM, Guido van Rossum wrote: >> (I wouldn't be surprised if there wasn't -- while computer clocks >> have a precision in nanoseconds, that doesn't mean they are that >> *accurate* at all (even with ntpd running). > > The real-world use cases deal with getting this information from other > devices (network cards, GPS, particle accelerators, etc.), so it's not > really a matter of cross-computer accurancy, but relative accuracy > (i.e. how long did something take?). It would be nice if it were possible to deal with high-precision epoch times and time deltas without special tricks. I have had to deal with femtosecond-precision IRL (albeit in a realtime C application, not in Python). Quad-precision floats (<URL: http://en.wikipedia.org/wiki/Quadruple-precision_floating-point_format>) would do it for Python: * just do it in seconds * have enough precision for any needs * have enough renge for any needs Marko
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4