Message196107
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:56 | r.david.murray | set | recipients:
+ r.david.murray, ezio.melotti, eric.araujo, flox, jdennis, julien.phalip |
2013-08-25 00:16:56 | r.david.murray | set | messageid: <1377389816.64.0.272756038987.issue16611@psf.upfronthosting.co.za> |
2013-08-25 00:16:56 | r.david.murray | link | issue16611 messages |
2013-08-25 00:16:55 | r.david.murray | create | |
|