[Python-Dev] pathlib difference to the backport (original) (raw)
Ionel Cristian Mărieș contact at ionelmc.ro
Mon Nov 10 12:45:57 CET 2014
- Previous message: [Python-Dev] Improvements for Pathlib
- Next message: [Python-Dev] pathlib difference to the backport
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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? It's also inconsistent, stat and all the methods that depend on stat do not implement the "is closed check" (raise ValueError if exit was already called).
Can anyone explain?
Thanks, -- Ionel M. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20141110/d3ac8e3f/attachment.html>
- Previous message: [Python-Dev] Improvements for Pathlib
- Next message: [Python-Dev] pathlib difference to the backport
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]