Oleg Broytman phd at phdru.name
Wed Apr 6 15:26:42 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 ]

---

On Wed, Apr 06, 2016 at 11:54:08AM -0700, Ethan Furman <ethan at stoneleaf.us> wrote:
> On 04/06/2016 11:32 AM, Brett Cannon wrote:
> >On Wed, 6 Apr 2016 at 11:06 Ethan Furman wrote:
> >>On 04/06/2016 10:26 AM, Brett Cannon wrote:
> 
> >>>Now we need clear details. :) Some open questions are:
> >>>
> >>> 1. Name: __path__, __fspath__, or something else?
> >>
> >>__fspath__
> >
> >+1 for __path__, +0 for __fspath__ (I don't know how widespread the
> >notion that "fs" means "file system" is).
> 
> Maybe __os_path__ then?  I would rather be explicit about the type of path
> we are dealing with -- who knows if we won't have __url_path__ in the future
> (besides Guido, of course ;)

   __pathstr__? __urlstr__?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

---

• 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