Éric Araujo mer...@netwok.org added the comment:
Éric, the docs clearly state that currently only full-line comments
are enabled by default.
Wow, I missed that. I use such comments in some config files or config file
examples in documentation :(
--
Éric Araujo mer...@netwok.org added the comment:
(Adding 3.x versions because we’ll want to add tests to them.)
--
nosy: +eric.araujo, lukasz.langa
versions: +Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
Łukasz Langa luk...@langa.pl added the comment:
Daniel, thank you for your report. Indeed, 3.2+ has an updated configparser
where we turned off support for inline comments (e.g. comments after option
values). This was decided after we discovered how inconsistent it is. Your
report shows this
New submission from Daniel Fortunov pythonbugtrac...@danielfortunov.com:
ConfigParser does not implement comments need to be preceded by a whitespace
character correctly and in most cases will treat a value beginning with a
comment character as a comment, even though it is not preceded by a
