On Tue, Apr 19, 2016, at 12:20, Guido van Rossum wrote:
> Also, I don't expect a future where bytes paths don't make sense, unless
> Linux starts enforcing a normalized UTF-8 encoding in the kernel.
Well, OSX does that now, but that's a whole other topic. Whether it is
useful to represent paths as the bytes type in Python code is orthogonal
to whether you can have paths that aren't valid strings in an encoding,
considering that surrogateescape lets you represent any sequence of
bytes as a str.