[issue43395] os.path states that bytes can't represent all MBCS paths under Windows

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue43395] os.path states that bytes can't represent all MBCS paths under Windows

Change by Eryk Sun : -- versions: -Python 3.6, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue43395] os.path states that bytes can't represent all MBCS paths under Windows

Eryk Sun added the comment: > instead of the stated 'surrogatepass' In Python 3.6 and above, you can check this as follows: >>> sys.getfilesystemencoding() 'utf-8' >>> sys.getfilesystemencodeerrors() 'surrogatepass' In Python 3.5 and previous: >>> sys.getfilesystemencodi

[issue43395] os.path states that bytes can't represent all MBCS paths under Windows

Eric L. added the comment: Very confusing but very interesting. I'm trying to follow as I'm the main maintainer of the rdiff-backup software, which goes cross-platforms, so these small differences might become important. Now, looking into the docs, following your explanations, I noticed that

[issue43395] os.path states that bytes can't represent all MBCS paths under Windows

Eryk Sun added the comment: > Vice versa, using bytes objects cannot represent all file names > on Windows (in the standard mbcs encoding), hence Windows > applications should use string objects to access all files. This is outdated advice that should be removed, or at least reworded to emp

[issue43395] os.path states that bytes can't represent all MBCS paths under Windows

New submission from Eric L. : The os.path documentation at https://docs.python.org/3/library/os.path.html states that: > Vice versa, using bytes objects cannot represent all file names on Windows > (in the standard mbcs encoding), hence Windows applications should use string > objects to acc