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 mwm
Recipients ggenellina, mwm
Date 2009-03-10.05:32:53
SpamBayes Score 6.0869563e-09
Marked as misclassified No
Message-id <1236663178.64.0.205833274456.issue5370@psf.upfronthosting.co.za>
In-reply-to
Content
I don't believe in documenting bugs instead of fixing them. If this bug
is going to stay in the code, I can either fix my install of Python to
have non-broken Pickle modules, or I can fix every third-party libraries
objects I use whose authors didn't worry about pickling them enough to
find this. The fornmer is almost certainly easier, given a little time.
Probably even easier than agreeing on proper document wording.

The __init__ case is different - there isn't a common use case (this one
comes from the standard library) for __init__ that breaks pickling, and
the problems tend to manifest in the resulting pickles, not in the
unpickling process.
History
Date User Action Args
2009-03-10 05:32:59mwmsetrecipients: + mwm, ggenellina
2009-03-10 05:32:58mwmsetmessageid: <1236663178.64.0.205833274456.issue5370@psf.upfronthosting.co.za>
2009-03-10 05:32:56mwmlinkissue5370 messages
2009-03-10 05:32:54mwmcreate