On Wed, Mar 30, 2016 at 9:45 PM, Koos Zevenhoven
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?
BTW, don't get me wrong, I'm sure os.scandir is great, even if I have not used it :). What I mean is that it's easier to change something that was added more recently, i.e. when there are no old codebases that depend on it. I just think we should get these things right, before it's too late.
On Sun, Mar 27, 2016 at 5:40 PM, Koos Zevenhoven
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