[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2011-02-21 Thread Jesús Cea Avión
Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-09 Thread Raymond Hettinger
Raymond Hettinger added the comment: Thanks for taking a look and opining. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-09 Thread Guido van Rossum
Guido van Rossum added the comment: On Tue, Jun 9, 2009 at 12:16 PM, Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > >> Ah. How about only doing back-translation when protocol=2 (or lower) >> is explicitly selected? > > Well, this is exactly what is implemented! Ah, I missed that

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-09 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Ah. How about only doing back-translation when protocol=2 (or lower) > is explicitly selected? Well, this is exactly what is implemented! > I don't much like that 3.0 will be to read pickles written by 3.1 with > the default protocol (i.e. 3), I suppose you

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-09 Thread Guido van Rossum
Guido van Rossum added the comment: Ah. How about only doing back-translation when protocol=2 (or lower) is explicitly selected? I don't much like that 3.0 will be to read pickles written by 3.1 with the default protocol (i.e. 3), but I don't mind breaking protocol 2, since that's most likely (

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-09 Thread Raymond Hettinger
Raymond Hettinger added the comment: I vaguely remember you rejecting a proposal along these lines when Brett was doing the library renaming. The patch (as applied) turns on the renaming automatically when used with protocol 2 (i.e. all object names are stored with their 2.x names, not their

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-09 Thread Guido van Rossum
Guido van Rossum added the comment: I'm not on IRC. What exactly is your question for me? What is Raymond's view? -- ___ Python tracker ___ _

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-09 Thread Antoine Pitrou
Antoine Pitrou added the comment: Guido, Raymond suggested we ask your input on this one, although it's obviously a bit late (the patch has been committed). -- nosy: +gvanrossum ___ Python tracker _

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-06 Thread Antoine Pitrou
Antoine Pitrou added the comment: I've added an entry in the what's new file in r73254. -- status: open -> closed ___ Python tracker ___ _

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-04 Thread Hagen Fürstenau
Hagen Fürstenau added the comment: I think it is worth noting that now some Python 3.1 protocol 2 pickles can't be read by Python 3.0. We probably don't have to do anything about that, but perhaps it should be mentioned somewhere? Docs, release notes? -- status: pending -> open ___

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-04 Thread Antoine Pitrou
Antoine Pitrou added the comment: Committed in r73236 in the hope that it gets a bit more testing before rc2/final. -- assignee: alexandre.vassalotti -> resolution: -> fixed stage: patch review -> committed/rejected status: open -> pending ___ Pyth

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-04 Thread Alexandre Vassalotti
Alexandre Vassalotti added the comment: Oops. Here is a new patch with _compat_pickle.py. -- Added file: http://bugs.python.org/file14186/compat_pickle7.diff ___ Python tracker _

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-03 Thread Hagen Fürstenau
Hagen Fürstenau added the comment: The latest patch is missing the file "Lib/_compat.pickle.py". (Seems as if you forgot to svn add it after patching.) -- nosy: +hagen ___ Python tracker ___

[issue6137] Make pickle generated by Python 3.x compatible with 2.x and vice-versa.

2009-06-03 Thread Alexandre Vassalotti
Alexandre Vassalotti added the comment: Here is an updated patch based on Antoine's latest patch. Summary of changes: * Updated docstrings of Pickler and Unpickler in the pickle module. * Fixed pickle._Pickler to consider fix_imports only for protocol < 3 * Made module name remapping in _pic