[Python-Dev] When should pathlib stop being provisional?
projetmbc at gmail.com
Thu Apr 7 01:24:42 EDT 2016
As a simple user, pathlib simplifies playing with paths. A lot of things
are easy to do. For example, Pathlib / "subfile" is so useful.
I also have a subclass of pathlib.Path on github that makes easy seeking
for files and directories.
So keep alive pathlib !
Le 6 avr. 2016 13:06, "Paul Moore" <p.f.moore at gmail.com> a écrit :
On 6 April 2016 at 00:45, Guido van Rossum <guido at python.org> wrote:
> This does sound like it's the crucial issue, and it is worth writing
> up clearly the pros and cons. Let's draft those lists in a thread
> (this one's fine) and then add them to the PEP. We can then decide to:
> - keep the status quo
> - change PurePath to inherit from str
> - decide it's never going to be settled and kill pathlib.py
> (And yes, I'm dead serious about the latter, rather Solomonic option.)
By the way, even if there's no solution that satisfies everyone to the
"inherit from str" question, I'd still be unhappy if pathlib
disappeared from the stdlib. It's useful for quick admin scripts that
don't justify an external dependency. Those typically do quite a bit
of path manipulation, and as such benefit from the improved API of
pathlib over os.path.
+1 on making (and documenting) a final decision on the "inherit from
-1 on removing pathlib just because that decision might not satisfy everyone
Python-Dev mailing list
Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev