Guido van Rossum <[EMAIL PROTECTED]> added the comment:
The issue is different; there is already a bug open for this (bug 2307).
--
nosy: +gvanrossum
resolution: -> invalid
status: open -> closed
superseder: -> Decide what to do with bytes/str when transferring pickles
between 2.6 and
New submission from Brett Cannon <[EMAIL PROTECTED]>:
It turns out that unpickling a string from 2.6 leads to a Unicode string
in 3.0. That might fail since the encoding was never specified. This
should be documented probably in both 2.6 and 3.0.
--
assignee: georg.brandl
components: Doc
