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 r.david.murray
Recipients eric.araujo, ezio.melotti, flox, jdennis, julien.phalip, r.david.murray
Date 2013-08-25.00:16:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think a fully logical fix could be implemented for 3.4 (after I commit this), because as you say it is *unlikely* that anyone is relying on the behaviors mentioned as "backward compatibility issues" in the added tests.  However, it is *possible* someone is dealing with a quirky situation where some other broken software is using these flags in key/value form, and depending on it.  Not likely, no (especially since the value would be lost on re-serialization), but since we *can* fix the issue without risking breaking such code, we should, for the maintenance release.
Date User Action Args
2013-08-25 00:16:56r.david.murraysetrecipients: + r.david.murray, ezio.melotti, eric.araujo, flox, jdennis, julien.phalip
2013-08-25 00:16:56r.david.murraysetmessageid: <>
2013-08-25 00:16:56r.david.murraylinkissue16611 messages
2013-08-25 00:16:55r.david.murraycreate