Ł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 decision was the right one.
As for 2.7 unfortunately it's long in maintenance mode now so no functional changes are possible. I've prepared a backport of the 3.2+ configparser for 2.6+. It is available on PyPI: http://pypi.python.org/pypi/configparser. Have a look, might solve your problem (and quite a bunch of others I suppose). Éric, the docs clearly state that currently only full-line comments are enabled by default. ---------- resolution: -> wont fix stage: -> committed/rejected status: open -> closed versions: -Python 3.2, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12862> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
