Kevin Norris added the comment:
I'm a little concerned about this fix. In particular, if I understand the
design of the patch correctly, it is intended to produce this behavior:
Path('C:/foo').resolve() != Path('//?/C:/foo').resolve()
Since both paths are valid and both paths refer to the same file, some
developers may find this result counterintuitive. The Path.resolve() docs do
not expressly forbid it, however.
How many developers assume Path.resolve() is always the same for the same file?
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22299>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
