[issue1524825] ConfigParser: accept leading whitespace on options+comments

Changes by Terry J. Reedy : -- superseder: -> ConfigParser support for alt delimiters ___ Python tracker ___ ___ Python-bugs-list m

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Changes by Michael Foord : -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Łukasz Langa added the comment: Implemented as part of issue1682942 since it touches the same code. Moreover, this issue mentions Samba config parsing in the original comment (msg50719) which was not doable without the changes introduced by issue1682942. So I would supersede this issue with i

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Terry J. Reedy added the comment: I closed #1714 as a duplicate of this. It also has a patch attached. -- nosy: +akuchling, christian.heimes, msuchy, schmir, tjreedy versions: +Python 3.2 -Python 2.6, Python 3.0 ___ Python tracker

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Jonatas Oliveira <[EMAIL PROTECTED]> added the comment: The patch cfgparser_comments.patch works for me. I agree with Jeremy Thurgood about the issue 1714. -- nosy: +jonatasoliveira _ Tracker <[EMAIL PROTECTED]>

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Jeremy Thurgood <[EMAIL PROTECTED]> added the comment: This looks very much like a duplicate of issue 1714. Perhaps the two should be merged? -- nosy: +jerith _ Tracker <[EMAIL PROTECTED]>

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Quentin Gallet-Gilles <[EMAIL PROTECTED]> added the comment: Didn't think "a few days" would translate into a month. My bad! Anyway, here's the promised patch. -- keywords: +patch Added file: http://bugs.python.org/file9848/cfgparser_comments.patch _

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Changes by Raghuram Devarakonda: -- nosy: +draghuram _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Quentin Gallet-Gilles added the comment: Okay, I'll upload a patch with unit tests and doc changes for the comment part in the next few days. _ Tracker <[EMAIL PROTECTED]> _

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Ken Lalonde added the comment: Quentin: I didn't appreciate the line-continuation issue. Breaking existing code is out of the question, so I'd like to retract that part of the patch. _ Tracker <[EMAIL PROTECTED]> _

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Quentin Gallet-Gilles added the comment: I tried to come up with a patch, but the issue isn't as easy as it seems, the proposed change is too simplistic. Leading spaces in a line is already used for one purpose : continuations of a previous line. For instance : option = value continued here giv

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Changes by Facundo Batista: -- keywords: +easy -patch _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1524825] ConfigParser: accept leading whitespace on options+comments

Changes by Georg Brandl: -- type: -> feature request versions: +Python 2.6, Python 3.0 _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bu