Message300717
I merged the original fix and documented it. I thought about it some more and remembered that RawConfigParser objects do in fact support non-string values by historical coincidence. It's unfortunately a popular idiom with old programs to load some configuration defaults using the `defaults=` keyword and later use the legacy get() and set() API which doesn't check types inside. A config file like this cannot be safely written back to a file, etc.
I would very much like to get rid of RawConfigParser entirely but we're stuck with it due to backwards compatibility. So, to fix the regression, I created PR 3191. |
|
Date |
User |
Action |
Args |
2017-08-22 19:06:09 | lukasz.langa | set | recipients:
+ lukasz.langa, r.david.murray, aragilar |
2017-08-22 19:06:09 | lukasz.langa | set | messageid: <1503428769.13.0.534116808815.issue23835@psf.upfronthosting.co.za> |
2017-08-22 19:06:09 | lukasz.langa | link | issue23835 messages |
2017-08-22 19:06:09 | lukasz.langa | create | |
|