➜

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 p-ganssle
Recipients alexandre.vassalotti, belopolsky, bronger, eddygeek, gregory.p.smith, p-ganssle, pitrou, serhiy.storchaka, tanzer@swing.co.at, tim.peters
Date 2018-12-07.15:03:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544195019.96.0.788709270274.issue22005@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm not sure I agree with how this was resolved. We're adding complexity to the datetime unpickler to support unpickling pickles created in Python 2 in Python 3? I also don't really understand the encoding parts of it, but it smells very fishy to me.

I agree with Gregory here, pickle has so many other problems when used between versions of Python that it's simply not useful for cross-version serialization. It is useful for things like inter-process communication between two trusted instances of Python programs running the same version.

Also, what is the plan here for 2020+? Do we remove this hack for Python 3.9, or are we stuck with it indefinitely?
History
Date User Action Args
2018-12-07 15:03:40p-gansslesetrecipients: + p-ganssle, tim.peters, gregory.p.smith, belopolsky, pitrou, bronger, alexandre.vassalotti, serhiy.storchaka, eddygeek, tanzer@swing.co.at
2018-12-07 15:03:39p-gansslesetmessageid: <1544195019.96.0.788709270274.issue22005@psf.upfronthosting.co.za>
2018-12-07 15:03:39p-gansslelinkissue22005 messages
2018-12-07 15:03:39p-gansslecreate