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 gregory.p.smith
Recipients alexandre.vassalotti, belopolsky, bronger, eddygeek, gregory.p.smith, pitrou, serhiy.storchaka,, tim.peters
Date 2017-03-02.18:57:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
TL;DR - Just one more example of why nobody should *ever* use pickle under any circumstances.  It is useless for data that is not transient for consumption by the same exact versions of all software that created it.

Patches against 2.7 are not useful here.  Either we write a unpickle deserializer for python 2 datetime pickles that works for all existing previous datatime pickled data formats from Python 3.  Or we close this as rejected because the data formats are rightly incompatible as the in-process object states are incompatible between the two versions.

If you want to serialize something, use a language agnostic data format - ideally one with a defined schema.  Never pickle.

Advice for those who have stored such data in Python 2 pickles: Write a Python 2 program to read your data and rewrite it in a portable data format that has nothing to do with pickle.  Anything else is a gross hack.
Date User Action Args
2017-03-02 18:57:18gregory.p.smithsetrecipients: + gregory.p.smith, tim.peters, belopolsky, pitrou, bronger, alexandre.vassalotti, serhiy.storchaka, eddygeek,
2017-03-02 18:57:18gregory.p.smithsetmessageid: <>
2017-03-02 18:57:18gregory.p.smithlinkissue22005 messages
2017-03-02 18:57:18gregory.p.smithcreate