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 alexandre.vassalotti
Recipients alexandre.vassalotti, mkiever, pitrou
Date 2009-05-31.00:09:23
SpamBayes Score 0.00017321527
Marked as misclassified No
Message-id <1243728585.59.0.943297098126.issue6137@psf.upfronthosting.co.za>
In-reply-to
Content
If I understood correctly, #3675 is about making pickle data generated
by Python 3 readable by Python 2. However, this issue is about
compatibility in the other direction—i.e., making Python 2 pickles
readable by Python 3, which is easier.

I have a patch that make Unpickler translates the old names to the new
ones at runtime. The only thing missing in the patch is the unit tests
since I am not sure this should be tested. I am thinking using the
approach Collin Winter used for his compatibility tests in #5665.
However, his approach requires bidirectional pickle compatibility
between Python 2 and 3, which we don't have.
History
Date User Action Args
2009-05-31 00:09:46alexandre.vassalottisetrecipients: + alexandre.vassalotti, pitrou, mkiever
2009-05-31 00:09:45alexandre.vassalottisetmessageid: <1243728585.59.0.943297098126.issue6137@psf.upfronthosting.co.za>
2009-05-31 00:09:42alexandre.vassalottilinkissue6137 messages
2009-05-31 00:09:40alexandre.vassalotticreate