Mike Meyer <m...@users.sourceforge.net> added the comment: 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. ---------- message_count: 4.0 -> 5.0 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5370> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
