2007/11/1, Guido van Rossum <[EMAIL PROTECTED]>: > I could leave this all up to the 3.0 application, which would have to > "fix up" any bytes in the pickle it receives explicitly if it wants > to. Alternatively, I could add an encoding option to the pickle > loading APIs (and for full flexibility an errors option as well) so > that at least simple text-based applications might have a chance of > reading the data that they themselves wrote before they were ported to > 3.0 with minimal changes (only the unpickling calls would have to be > modified).
I think that to make possible to the unpickling appl to specify which encoding to use is the best option here, so to avoid: - Need to change the appl that created the pickle (that can be not accesible). - Have to make the work by hand of dealing with that "fix up" everywhere. - Requests from developers to add a "magic guess" to discover automatically which encoding use. Regards, -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
