Antoine Pitrou <pit...@free.fr> added the comment: > > So, IMO, practicality beats purity here. Especially since it is bound to > > land in a bugfix release (3.2.1), which users don't expect to produce > > regressions in their own code. > > Nope. Your suggestion would be a new feature and those are not > allowed in patch level releases.
What new feature are you talking about? I think you misunderstood the actual issue: NULL as an empty string *worked* in 3.1 and that's why we have a regression with _pickle here. So, in the end, you are the one proposing a change in actual behaviour, while I'm trying to minimize changes (and breakage). ---------- title: Some "trivial" python 2.x pickles fails to load in Python 3.2 -> Some "trivial" python 2.x pickles fails to load in Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11286> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
