<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 11.04.2016 22:55, Alexander Walters wrote:<br>
<blockquote cite="mid:570C0F29.5010904@sdamon.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Every conceivable way to fix pathlib have already been argued.
Are any of them worth doing? Can we get consensus enough to
implement one of them? If not, we should consider either dropping
the matter or dropping the module.<br>
</blockquote>
<br>
Right now, I don't see pathlib removed. Why? Because using strings
alone has its caveats (we all know that). So, I cannot imagine an
alternative concept to pathlib right now. We might call it
differently, but the concept stays unchanged.<br>
<br>
MAYBE, if there's an alternative concept, I could be convinced to
support dropping the module.<br>
<br>
Best,<br>
Sven<br>
<br>
PS: The only way out that I can imagine is to fix pathlib. I am not
in favor of fixing functions of "os" and "os.path" to except "path"
objects; which does the majority here discuss now with the new
__fspath__ protocol. But shaping what we have is definitely worth
it.<br>
</body>
</html>