[Python-Dev] pathlib difference to the backport (original) (raw)
Ionel Cristian Mărieș contact at ionelmc.ro
Mon Nov 10 18:10:14 CET 2014
- Previous message: [Python-Dev] pathlib difference to the backport
- Next message: [Python-Dev] py34 makes it harder to read all of a pty
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Speaking of that, shouldn't pathlib have support for dir_fd?
Thanks, -- Ionel M.
On Mon, Nov 10, 2014 at 6:53 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
On Mon, 10 Nov 2014 13:45:57 +0200 Ionel Cristian Mărieș <contact at ionelmc.ro> wrote: > Hey, > > It appears there's a peculiar difference between the pathlib in the 3.4 > branch and the one on bitbucket: cpython's pathlib.Path implements a no-op > context manager interface. What's the purpose of that?
Hum... That's a remnant of the various pathlib prototypes, where this was used for the openat()-based implementation. It should probably be removed. Regards Antoine.
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/contact%40ionelmc.ro -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20141110/787e2f34/attachment.html>
- Previous message: [Python-Dev] pathlib difference to the backport
- Next message: [Python-Dev] py34 makes it harder to read all of a pty
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]