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 larry
Recipients larry
Date 2011-09-05.21:50:13
SpamBayes Score 1.019148e-06
Marked as misclassified No
Message-id <>
A small aside:

An IEEE 754 double is insufficient to store a modern timestamp with nanosecond accuracy.  We're currently at just over 1.3 billion seconds since the epoch.  This eats 28 bits of the mantissa.  (The value is actually 31 bits to the left of the decimal point, but you get the leading 1 and the subsequent two 0s for free.)  Precisely storing a billion values to the right of the decimal point would require another 30 bits.  The mantissa of a double is sadly only 52 bits.  So we're shy by 6 bits, give or take.

So this patch doesn't make Python 100% accurate with respect to atime/mtime.  What it *does* do is makes Python's loss of accuracy consistent.  I claim that's a definite improvement.
Date User Action Args
2011-09-05 21:50:14larrysetrecipients: + larry
2011-09-05 21:50:13larrysetmessageid: <>
2011-09-05 21:50:13larrylinkissue12904 messages
2011-09-05 21:50:13larrycreate