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 wrote:
> On Mon, 10 Nov 2014 13:45:57 +0200
> Ionel Cristian Mărieș wrote:
> > Hey,
> >
> > It appears there's a peculiar difference between the pathlib in the 3.4
On Mon, 10 Nov 2014 13:45:57 +0200
Ionel Cristian Mărieș 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
I disagree, having pathlib support in just one place in stdlib is in fact
what's really inconsistent. Also, I'm pretty sure that sprinkling pathlib
support all over the stdlib isn't going to be pretty.
Thanks,
-- Ionel M.
On Sun, Nov 9, 2014 at 12:06 AM, Xavier Morel
wrote:
> On 2014-11-08, at
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 "
On Saturday, November 8, 2014, Xavier Morel wrote:
>
>
> Why would pathlib need to provide this when tempfile already does?
>
> with tempfile.NamedTemporaryFile(prefix='') as f:
> tmp = pathlib.Path(f.name)
>
> with tempfile.TemporaryDirectoryDirectory(prefix='') as d:
> tmp = pat
Hi,
some background about my pathlib usage.
I use the backported version of pathlib and tried to replace the usage of
path.py (also widely used library).
Some features part of path.py missing in pathlib:
- expanduser, expandvars, I have to use the os functions to do this.
It is possible but be
