[Python-Dev] Defining a path protocol
Glenn Linderman
v+python at g.nevcal.com
Wed Apr 6 20:21:03 EDT 2016
More information about the Python-Dev mailing list
Wed Apr 6 20:21:03 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 4/6/2016 4:44 PM, Ethan Furman wrote: > On 04/06/2016 04:27 PM, Brett Cannon wrote: >> On Wed, 6 Apr 2016 at 15:54 Gregory P. Smithwrote: >>> >>> So would module.__path__ become a Path instance in a potential >>> future making module.__path__.__path__ meaningfully confusing? ;) >>> >>> I'm not worried about people who shove pathlib.Path instances in as >>> values into sys.modules and expect anything but pain. :P >> >> Ah, good point. I think that kills __path__ then as an option. > > Excellent! Narrowing the field then to: > > __fspath__ -1: not all os names that look like files actually refer to the file system: pipes, devices, etc. > > __os_path__ +1: the special names are os dependent, so os seems like an appropriate prefix. > > > Step right up! Cast yer votes! > > -- > ~Ethan~ > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/v%2Bpython%40g.nevcal.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160406/2e857796/attachment.html>
- 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