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 pitrou
Recipients Arfrever, Niklas.Claesson, Ramchandra Apte, andrewclegg, belopolsky, goshawk, lemburg, pitrou, r.david.murray, tim.peters, vstinner
Date 2014-07-15.13:26:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <53C52C00.40700@free.fr>
In-reply-to <1405392821.23.0.851273600966.issue15443@psf.upfronthosting.co.za>
Content
Le 14/07/2014 22:53, Tim Peters a écrit :
>
> That consumes exactly 10 bytes today. Add nanoseconds, and it will
take at least 11 (if 4 bits are insanely squashed into the bytes
currently devoted to microseconds), and more likely 12 (if nanoseconds
are sanely given their own 2 bytes).

That doesn't have to be. For example you could use the MSB of the 
microseconds field to store a "datetime pickle flags" byte, which could 
tell the unserializer whether a nanoseconds (or attoseconds :-)) field 
follows or not.

Remember that existing pickles must remain readable, so there must be 
some kind of version field anyway.
History
Date User Action Args
2014-07-15 13:26:27pitrousetrecipients: + pitrou, lemburg, tim.peters, belopolsky, vstinner, Arfrever, r.david.murray, andrewclegg, Ramchandra Apte, goshawk, Niklas.Claesson
2014-07-15 13:26:27pitroulinkissue15443 messages
2014-07-15 13:26:27pitroucreate