I really like pathlib.
But for a while is was painful to use, 'cause there was som much code that still used strings for paths. That was made a lot better when we introduced the __fspath__ protocol, and then updated the standard library to use it (everywhere?).
But there are still a few that bug me. For instance:
__file__ is a path represented as a string. It's not too big a deal to wrap it in Path(), but it still annoys me.
So: would it be entirely too disruptive to replace these kinds of things with Path objects?
Christopher Barker, PhD
Python Language Consulting
- Scientific Software Development
- Desktop GUI and Web Development
- wxPython, numpy, scipy, Cython