➜

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 vstinner
Recipients belopolsky, loewis, tim.peters, vstinner
Date 2014-08-25.01:45:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1408931153.11.0.791614914428.issue22117@psf.upfronthosting.co.za>
In-reply-to
Content 
Instead of a complex structure, we can use a 64-bit signed integer to store a number of nanoseconds. For a UNIX epoch, nanoseconds since January 1st 1970, the min/max are:
1677-09-21 00:12:43.145224
2262-04-11 23:47:16.854776

The Linux kernel is going to use 64-bit integer even on 32-bit CPU to store timestamps, to simplify the code (to avoid the structure).
History
Date User Action Args
2014-08-25 01:45:53vstinnersetrecipients: + vstinner, tim.peters, loewis, belopolsky
2014-08-25 01:45:53vstinnersetmessageid: <1408931153.11.0.791614914428.issue22117@psf.upfronthosting.co.za>
2014-08-25 01:45:53vstinnerlinkissue22117 messages
2014-08-25 01:45:52vstinnercreate