Message268403
Would you consider raising an exception at least for the case of a "To:" header or perhaps a warning or someother failsafe.
Using __setitem__ for appending instead of replacement is surprising and in the case of LetsEncrypt was a small disaster. There is a docstring explaining what is going on but that typically isn't visible to the user of the square brackets operator.
For Python3.6, I think there should be an alternative API that doesn't use the square brackets operator: add_header, replace_header, remove_header or somesuch. The problem is that square brackets never suggests appending which is what is actually happening. |
|
Date |
User |
Action |
Args |
2016-06-12 21:19:07 | rhettinger | set | recipients:
+ rhettinger, barry, kxroberto, r.david.murray, adrien-saladin, python-dev, berker.peksag |
2016-06-12 21:19:07 | rhettinger | set | messageid: <1465766347.86.0.583183306903.issue10839@psf.upfronthosting.co.za> |
2016-06-12 21:19:07 | rhettinger | link | issue10839 messages |
2016-06-12 21:19:07 | rhettinger | create | |
|