[Python-Dev] Defining a path protocol
Greg Ewing
greg.ewing at canterbury.ac.nz
Fri Apr 8 01:59:43 EDT 2016
More information about the Python-Dev mailing list
Fri Apr 8 01:59:43 EDT 2016
- Previous message (by thread): [Python-Dev] Defining a path protocol
- Next message (by thread): [Python-Dev] Defining a path protocol
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): [Python-Dev] Defining a path protocol
- Next message (by thread): [Python-Dev] Defining a path protocol
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list