On Wed, Mar 30, 2016 at 9:26 PM, Brett Cannon <brett@python.org> wrote:
The `.path` attribute, which seems a silly name, I look at as being necessary for compatibility with DirEntry.
I don't remember the exact issue that tracked the discussion, but there was back-and-forth on that attribute name and in the end Guido chose `path`.
This one: https://bugs.python.org/issue22570 See my comment below (from this thread, but there were no reactions). I'm not sure if that option was ever considered. Can we let DirEntry dictate the future of Python? On Sun, Mar 27, 2016 at 5:40 PM, Koos Zevenhoven <k7hoven@gmail.com> wrote:
Actually, now that .path is not out yet, would it make sense to call it Path.str or Path.strpath instead, and introduce the same thing on DirEntry and guarantee a str (instead of str or bytes as DirEntry.path now does)? Maybe that would lead to fewer broken implementations in third-party libraries too?
-Koos