[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Alexandre Vassalotti added the comment: Superseded by issue #6137. -- resolution: -> duplicate status: open -> closed superseder: -> Make pickle generated by Python 3.x compatible with 2.x and vice-versa. ___ Python tracker

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Changes by Collin Winter : -- nosy: +collinwinter ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Alexandre Vassalotti added the comment: Would it would be sufficient to add a function in the pickletools capable of converting old Python 2 pickles to the new format in Python 3? Alternatively, we could add a compatibility Unpickler class that would override the find_class method to do the name

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Changes by Antoine Pitrou : -- versions: +Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: I agree with Antoine, protocols <= 2 should remain compatible with Python 2.x or be deprecated. Keeping compatibility will require a hack, in addition to the proposed patch, in Pickler.save_global to map Python 3's module names to the on

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > Was it really intended that 3.0 pickles unpickle on 2.6? He used protocol 2, so he explicitly asked for something inpickleable with 2.6. If it's not the intended behaviour, then protocols < 3 should be deprecated. -- nosy: +pitrou

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: Was it really intended that 3.0 pickles unpickle on 2.6? What about other changes like moving something from one module to another (reduce from built-in to functools), changing all classes to new style (several examples), or adding methods to

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Daniel Diniz <[EMAIL PROTECTED]> added the comment: FWIW, there's a mapping of 2.6:3.0 modules in lib2to3: from lib2to3.fixes.fix_imports import MAPPING The attached patch uses that for a quick and dirty way of loading 3.0 pickles in 2.6. -- keywords: +patch Added file: http://bugs.pyt

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Hagen Fürstenau <[EMAIL PROTECTED]> added the comment: Well, Python <= 2.5 still wouldn't be able to unpickle those built in objects. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Daniel Diniz <[EMAIL PROTECTED]> added the comment: Hagen, does this simple patch (against 2.6) solve it for you? Index: Lib/pickle.py === --- Lib/pickle.py (revision 66050) +++ Lib/pickle.py (working copy) @@ -1121,6 +1

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Hagen Fürstenau <[EMAIL PROTECTED]> added the comment: Well, this is obviously caused by renaming "__builtin__" to "builtins" and the fact that set (as well as frozenset) doesn't have its own opcode and therefore gets looked up in "builtins". The problem therefore extends to all builtin objects w

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- nosy: +alexandre.vassalotti priority: -> critical type: -> behavior ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3675] Python 2.6 can't read sets pickled with Python 3.0

New submission from Hagen Fürstenau <[EMAIL PROTECTED]>: After pickling a set of ints with Python 3.0 and pickle protocol 2: [EMAIL PROTECTED] ~]$ python3.0 Python 3.0b3 (r30b3:65927, Aug 21 2008, 11:48:29) [GCC 4.1.0 20060304 (Red Hat 4.1.0-3)] on linux2 Type "help", "copyright", "credits" or "