Message237728
> I think that for consistency either parse empty name-value pair as key="", value=None
There is already a test present (https://hg.python.org/cpython/file/0469af231d22/Lib/test/test_http_cookiejar.py#l1084) that ensures an unset name/value pair is ignored altogether, so I don't think that makes sense from a backwards compatibility standpoint. For consistency, I kept the functionality where nameless cookies are ignored (i.e. "=foo"). I think that while it may be breaking backwards compatibility for buggy edge cases, it's more consistent with existing functionality and actually conforms to the RFC. That said, I'm not going to argue over it heatedly, so if you'd still rather see those cases permitted, let me know and I'll change it.
Valueless cookies are still permitted to keep backwards compatible as there are existing tests for that. |
|
Date |
User |
Action |
Args |
2015-03-10 05:41:34 | demian.brecht | set | recipients:
+ demian.brecht, BreamoreBoy, berker.peksag, serhiy.storchaka, chfoo |
2015-03-10 05:41:34 | demian.brecht | set | messageid: <1425966094.78.0.339669565284.issue23138@psf.upfronthosting.co.za> |
2015-03-10 05:41:34 | demian.brecht | link | issue23138 messages |
2015-03-10 05:41:34 | demian.brecht | create | |
|