Bah, unexpected keyboard shortcut - sorry for the premature send...
On 29 March 2016 at 13:10, Paul Moore firstname.lastname@example.org wrote:
However, it does mean that certain use cases are not supported by pathlib. One of the constant issues with core/stdlib development is having to consider how the design affects people with needs you don't personally have. This one's not such a big problem "pathlib doesn't support non-Unicode filenames" is a simple enough to express limitation. But that doesn't help the poor guy debugging an issue with his filesystem-scanning program where a user has a mangled non-Unicode filename somewhere in the bowels of his profile - does he declare that user's situation is unsupported, or does he abandon pathlib in favour of the old os APIs? (And if the , what's the likelihood
(And either way, what's the likelihood of him ever wanting to use pathlib again?)