Related:https://github.com/python/cpython/pull/242https://bugs.python.org/issue29623In the discussion over my PR forbpo-29623 it became clear that bytestring paths were also unsupported and it was suggested that that should be a separate issue (currently the PR adds checks for both types).There is some possible odd behaviour as when given a bytestring path the method attempts to open the integer file descriptors for each character in the bytestring. This will most likely fail silently but if it does find an actual file descriptor it will attempt to read and then close the file.Example from the discussion on the PR:>>> import os>>> import configparser>>> k = os.open('/home/david/develop/cpython/Lib/test/cfgparser.1', os.O_RDONLY)>>> k3>>> c = configparser.ConfigParser()>>> c.read(b'\x03') [3]>>> list(c)['DEFAULT', 'Foo Bar']>>> os.close(k)  # File has already been closedOSError: [Errno 9] Bad file descriptorCurrently bytestrings do work correctly when provided as part of a list.