[issue35002] Potential bug in ConfigParser.read() in python3.6, before os.Pathlike was introduced

Berker Peksag added the comment: Unfortunately, we can't accept this change for 3.5 either because it's now in security-fix-only mode. See https://devguide.python.org/#status-of-python-branches for more details about the status of branches in the CPython repository. Thank you for spending

[issue35002] Potential bug in ConfigParser.read() in python3.6, before os.Pathlike was introduced

Change by Luna Chen : -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue35002] Potential bug in ConfigParser.read() in python3.6, before os.Pathlike was introduced

Luna Chen added the comment: Hi Berker, Yes this workaround is mostly for python3.6.0. I have noticed my PR won't let me get to that version it seems. :( This bug seems to be present for python 3.5 as well. Would you recommend adding the fix to 3.5 instead or just simply close it? Thanks

[issue35002] Potential bug in ConfigParser.read() in python3.6, before os.Pathlike was introduced

Berker Peksag added the comment: Unless I'm missing something, you want the following snippet work in 3.6.0, right? import configparser as c import pathlib as p cp = c.ConfigParser() cp.read(p.Path('t.cfg')) t.cfg: $ cat t.cfg [Spam] foo = bar Support for

[issue35002] Potential bug in ConfigParser.read() in python3.6, before os.Pathlike was introduced

Change by Luna Chen : -- keywords: +patch pull_requests: +9274 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue35002] Potential bug in ConfigParser.read() in python3.6, before os.Pathlike was introduced

New submission from Luna Chen : In `configparser.ConfigParser.read()`, it allows us to pass in either a single filepath or a list of filepath. As python3 supports pathlib Path. We can potentially pass in a `PosixPath` to `configparser.ConfigParser.read()`, especially when passing in a list