On 04/06/2016 12:32 PM, Paul Moore wrote: > But I'm not one of the people who disliked using .path, so I'm > probably not best placed to judge. It would be good if someone who > *does* feel strongly could explain why fspath(pathobj) is better than > pathobj.path. fspath() would be useful because you can pass it a str or a Path and get a str back (or an exception if you pass the wrong thing in). Just like with Path you can pass a str or a Path get a Path back (or an exception if ...). -- -- ~Ethan~
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