[Python-Dev] Defining a path protocol
Wes Turner
wes.turner at gmail.com
Wed Apr 6 22:24:19 EDT 2016
More information about the Python-Dev mailing list
Wed Apr 6 22:24:19 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 Apr 6, 2016 6:31 PM, "Brett Cannon" <brett at python.org> wrote: > > > > On Wed, 6 Apr 2016 at 16:25 Nathaniel Smith <njs at pobox.com> wrote: >> >> On Wed, Apr 6, 2016 at 3:46 PM, Brett Cannon <brett at python.org> wrote: >> > >> > >> > On Wed, 6 Apr 2016 at 15:22 Paul Moore <p.f.moore at gmail.com> wrote: >> >> >> >> So I think we need a builtin. >> > >> > >> > Well, the ugliness shouldn't survive forever if the community shifts over to >> > using pathlib while the built-in will. We also don't have a built-in for >> > __index__() so it depends on whether we expect this sort of thing to be the >> > purview of library authors or if normal people will be interacting with it >> > (it's probably both during the transition, but I don't know afterwards). >> >> For __index__ the "built-in" is: >> >> from operator import index > > > Which suggests perhaps we should have pathlib.fspath() instead of a built-in. Would it make sense to instead have pathlib.Path.__init__? > > _______________________________________________ > 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/wes.turner%40gmail.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160406/c2e68bcf/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