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 kristjan.jonsson
Recipients georg.brandl, jcea, kristjan.jonsson, loewis, michael.foord, pitrou, rhettinger, sbt
Date 2012-03-27.12:09:00
SpamBayes Score 1.269002e-06
Marked as misclassified No
Message-id <1332850142.19.0.0102246859862.issue14288@psf.upfronthosting.co.za>
In-reply-to
Content
Btw, regarding compatibility:  The docs say " The pickle serialization format is guaranteed to be backwards compatible across Python releases."

I take this to mean the serialization format itself.  I don't think there is a broader guarantee that pickles generated by one version can be read by another, since objects can change their internal representation, types can even disappear or change.

In that sense, pickles made by 2.7 can be read by 3.2, in the sense that they will correctly return an error when they can't construct a 'str' object.

If I misunderstand things, then at least I think that the pickle documentation should be made clearer, that not only is the protocol supposed to be read, but also that entire pickles should always be readable _and_ instantiatable, by future versions
History
Date User Action Args
2012-03-27 12:09:02kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, georg.brandl, rhettinger, jcea, pitrou, michael.foord, sbt
2012-03-27 12:09:02kristjan.jonssonsetmessageid: <1332850142.19.0.0102246859862.issue14288@psf.upfronthosting.co.za>
2012-03-27 12:09:01kristjan.jonssonlinkissue14288 messages
2012-03-27 12:09:00kristjan.jonssoncreate