Nick Coghlan wrote: > Similar to my proposal for dealing with DirEntry.path being a > bytes-like object, I'd like to suggest raising TypeError in __fspath__ > if the request is nonsensical for the currently running system - *nix > systems can *manipulate* Windows paths (and vice-versa), but actually > trying to *use* them with the local filesystem isn't going to work > properly, since the syntax and semantics are different. That sounds reasonable, since it would be preferable to fail early if you mistakenly pass a PureWindowsPath to e.g. open(). But there needs to be some way to ask a path object for its native string representation, otherwise there would be no point in using foreign path objects at all. -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4