On 4/25/2014 12:46 PM, Fred Drake wrote: > On Fri, Apr 25, 2014 at 10:22 AM, Florian Bruhin <me at the-compiler.org> wrote: >> While it seems ConfigParser doesn't do any escaping as all, I'm >> thinking it should at least raise some exception when such a value is >> trying to be set. >> >> I'd expect writing something and then reading it back via the same >> configparser to *always* result in the same data, as long as writing >> worked without error. >> >> Thoughts? Should I submit a bug report? > > I believe you should, if only to provide a place to record why no > change gets made. When you do, add lukasz.langa as nosy https://docs.python.org/devguide/experts.html#experts You might also take a look in test/test_configparser.py to see if any edge cases are tested for. > Had ConfigParser been more careful from the beginning, that would have > been really good. > > At this point, it would be a backward-incompatible change, so it's > unlikely such a change could be allowed to affect existing code. > > > -Fred > -- Terry Jan Reedy
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4