[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Changes by Donald Stufft : -- pull_requests: +1059 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Serhiy Storchaka added the comment: Would be nice to add Misc/NEWS entry for this patch. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Florian Höch added the comment: > Thanks for your patch! As you can see, 2.7 is no longer touched as the codebases diverged. Thanks, although I have to say it's a little bit unfortunate that Python 2.7 will be left in a worse state than 2.6 where this bug did not exist. --

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Ned Deily added the comment: After discussing this offline with Łukasz, I'm going to take the risk of allowing the non-conforming 3.6 checkin to remain in for 3.6.0. -- nosy: +ned.deily ___ Python tracker

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Serhiy Storchaka added the comment: Is this release critical for 3.6.0? -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-b

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Łukasz Langa added the comment: Thanks for your patch! As you can see, 2.7 is no longer touched as the codebases diverged. I'll release a 3.6 backport on PyPI sometime this weekend that you can use. -- resolution: -> fixed status: open -> closed versions: +Python 3.5, Python 3.6, Pyth

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Roundup Robot added the comment: New changeset 40567b8e3478 by Łukasz Langa in branch '3.5': Fixes #24142: [configparser] always join multiline values to not leave the parser in an invalid state https://hg.python.org/cpython/rev/40567b8e3478 New changeset 306cfb866399 by Łukasz Langa in branch

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Florian Höch added the comment: It seems this hasn't landed yet? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

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

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Changes by Ned Deily : -- nosy: -ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Ned Deily added the comment: [Thanks for the headsup about the contributor agreement form, now reported as https://github.com/python/pythondotorg/issues/747] -- nosy: +ned.deily ___ Python tracker

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Changes by R. David Murray : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

Florian Höch added the comment: [Btw, you might want to fix the contributor agreement form - I can't sign it because it shows no text, so I don't know what I'm supposed to enter in the fields (Firefox 37.0.2)] -- ___ Python tracker

[issue24142] ConfigParser._read doesn't join multi-line values collected while reading if a ParsingError occured

New submission from Florian Höch: If a ParsingError occurs while reading a config file, the multi-line values collected while reading will never be joined because the error is raised before this can happen. This leads to very unexpected results, e.g. consider the following config.ini: [DEFAUL