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 loewis
Recipients georg.brandl, jcea, kristjan.jonsson, loewis, michael.foord, pitrou, rhettinger, sbt
Date 2012-03-24.23:51:38
SpamBayes Score 1.9121593e-11
Marked as misclassified No
Message-id <1332633099.71.0.288623033645.issue14288@psf.upfronthosting.co.za>
In-reply-to
Content
I think the "worth doing" argument doesn't really hold, given that it's done. The question at hand really is
a) is the patch correct?
b) can we commit to maintaining it, even as things around it may change?

I'm not bothered with the patch being potentially incomplete: anybody wishing to pickle more things should contribute patches for that.

As for a), I think we should give people some time to review, and then wait for beta releases to discover issues. If this is a rarely-used feature, the world won't end if it has bugs.

As for b), I think the main issue is forward compatibility: will pickles created by 3.3 still be readable by future versions?
History
Date User Action Args
2012-03-24 23:51:39loewissetrecipients: + loewis, georg.brandl, rhettinger, jcea, pitrou, kristjan.jonsson, michael.foord, sbt
2012-03-24 23:51:39loewissetmessageid: <1332633099.71.0.288623033645.issue14288@psf.upfronthosting.co.za>
2012-03-24 23:51:39loewislinkissue14288 messages
2012-03-24 23:51:38loewiscreate