[Python-ideas] Promoting the adoption of pathlib [Was: Working with Path objects: p-strings?]

[Alexander Walters]

I think this is missing step zero.  What does pathlib even offer me, the 
library developer?  Why should I use it?  I cannot be the only person 
who does not understand why it exists, let alone why I should be using 
it in my libraries.

On 3/31/2016 06:59, Paul Moore wrote:
> 1. Which interface (the str or the path one) gets the "obvious" name?
> Backward compatibility pretty much dictates it'd be the str version.
> 2. How do I support Python 2.7? And Python 3.3/3.4 (where the ".path"
> attribute doesn't exist)?
> 3. What's my transition plan for the future when I deprecate the str
> interface and only support path objects?
> 4. What will my users have to do if they want to use Path objects in
> their code? And how do I minimise their pain in doing so?