Chris Angelico wrote: > -1 for __os_path__, unless it's reasonable to justify it as "most of > the standard library uses Path objects, but os.path uses strings, so > before you pass a Path to anything in os.path, you call path.ospath() > on it, which calls __os_path__()". A less roundabout interpretation would be that it returns the path in a form that is directly acceptable to the OS. BTW, if __fspath__ is acceptable, __ospath__ (without the embedded _) should be as well. -- 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