[issue29627] configparser.ConfigParser.read() has undocumented/unexpected behaviour when given a bytestring path.

2017-09-07 Thread Vincent Michel
Changes by Vincent Michel : -- pull_requests: +3418 ___ Python tracker ___ ___

[issue29627] configparser.ConfigParser.read() has undocumented/unexpected behaviour when given a bytestring path.

2017-09-05 Thread Łukasz Langa
Changes by Łukasz Langa : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> ConfigParser.read silently fails if filenames argument is a byte string ___ Python tracker

[issue29627] configparser.ConfigParser.read() has undocumented/unexpected behaviour when given a bytestring path.

2017-02-22 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +lukasz.langa ___ Python tracker ___ ___

[issue29627] configparser.ConfigParser.read() has undocumented/unexpected behaviour when given a bytestring path.

2017-02-22 Thread David Ellis
New submission from David Ellis: Related: https://github.com/python/cpython/pull/242 https://bugs.python.org/issue29623 In the discussion over my PR for bpo-29623 it became clear that bytestring paths were also unsupported and it was suggested that that should be a separate issue (currently