➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients Arfrever, belopolsky, goshawk, lemburg, r.david.murray, vstinner
Date 2012-07-25.11:24:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343215469.78.0.23187921367.issue15443@psf.upfronthosting.co.za>
In-reply-to
Content 
On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg <report@bugs.python.org> wrote:
> ... full C double precision for the time part of a timestamp,
> which covers nanoseconds just fine.

No, it does not:

>>> import time
>>> t = time.time()
>>> t + 5e-9 == t
True

In fact, C double precision is barely enough to cover microseconds:

>>> t + 1e-6 == t
False

>>> t + 1e-7 == t
True
History
Date User Action Args
2012-07-25 11:24:29belopolskysetrecipients: + belopolsky, lemburg, vstinner, Arfrever, r.david.murray, goshawk
2012-07-25 11:24:29belopolskysetmessageid: <1343215469.78.0.23187921367.issue15443@psf.upfronthosting.co.za>
2012-07-25 11:24:29belopolskylinkissue15443 messages
2012-07-25 11:24:29belopolskycreate