[issue19461] RawConfigParser modifies empty strings unconditionally

2014-09-04 Thread Łukasz Langa
Łukasz Langa added the comment: This bug has been fixed in Python 3.2 (see 892236137db9). Please use the configparser backport for Python 2.7. -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed type: enhancement -> behavior __

[issue19461] RawConfigParser modifies empty strings unconditionally

2014-03-08 Thread Norman Denayer
Norman Denayer added the comment: I guess it's logical to have the value "" turned to '' in the reader, but I would expect the same transformation in the writer. If the write function would write "" for an empty string, will it solve your issue? -- keywords: +patch nosy: +Norman.Denay

[issue19461] RawConfigParser modifies empty strings unconditionally

2013-11-10 Thread Łukasz Langa
Changes by Łukasz Langa : -- assignee: -> lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue19461] RawConfigParser modifies empty strings unconditionally

2013-10-31 Thread R. David Murray
R. David Murray added the comment: A configurable option is probably the only way forward, due to backward compatibility reasons, but Łukasz will know for sure. If so, it can only go in the *next* version of Python, and while we haven't hit beta yet on 3.4 it may be too late for anyone to hav

[issue19461] RawConfigParser modifies empty strings unconditionally

2013-10-31 Thread Nacsa Kristóf
Nacsa Kristóf added the comment: typo: `key=` instead of `key=value` was meant as `key=` instead of `key=""` -- ___ Python tracker ___ _

[issue19461] RawConfigParser modifies empty strings unconditionally

2013-10-31 Thread Nacsa Kristóf
New submission from Nacsa Kristóf: http://hg.python.org/cpython/file/8d5df9602a72/Lib/ConfigParser.py#l529 RawConfigParser has a special case of replacing '""' with '' in reader. However the writer does not do the same. This may cause problems, for example if you merge multiple ini files into o