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 tim.peters
Recipients Arfrever, Niklas.Claesson, Ramchandra Apte, andrewclegg, belopolsky, goshawk, lemburg, pitrou, r.david.murray, tim.peters, vstinner
Date 2014-07-15.01:00:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A note from Guido, from about 2 years ago:

TBH, I think that adding nanosecond precision to the datetime type is
not unthinkable. You'll have to come up with some clever backward
compatibility in the API though, and that will probably be a bit ugly
(you'd have a microsecond parameter with a range of 0-1000000 and a
nanosecond parameter with a range of 0-1000). Also the space it takes
in memory would probably increase (there's no room for an extra 10
bits in the carefully arranged 8-byte internal representation).

Add pickle, etc.
Date User Action Args
2014-07-15 01:00:26tim.peterssetrecipients: + tim.peters, lemburg, belopolsky, pitrou, vstinner, Arfrever, r.david.murray, andrewclegg, Ramchandra Apte, goshawk, Niklas.Claesson
2014-07-15 01:00:26tim.peterssetmessageid: <>
2014-07-15 01:00:26tim.peterslinkissue15443 messages
2014-07-15 01:00:25tim.peterscreate