[issue46287] UNC path normalisation issues on Windows

Change by Eryk Sun : -- Removed message: https://bugs.python.org/msg410068 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46287] UNC path normalisation issues on Windows

neonene added the comment: > PathCchSkipRoot() doesn't recognize forward slash as a path separator, I opened issue46362 and PR30571 about the mentioned abspath() behaviors. -- ___ Python tracker

[issue46287] UNC path normalisation issues on Windows

Eryk Sun added the comment: > _Py_abspath/_getfullpathname does not always call GetFullPathNameW on 3.11. Also, PathCchSkipRoot() doesn't recognize forward slash as a path separator, so _Py_isabs() is wrong in many cases compared to the same path that uses backslash as the path separator.

[issue46287] UNC path normalisation issues on Windows

neonene added the comment: Regarding https://github.com/python/cpython/pull/30362#issuecomment-1005496892 _Py_abspath/_getfullpathname does not always call GetFullPathNameW on 3.11. Python 3.10.1 >>> nt._getfullpathname('.\\C:spameggs. . .') '.\\C:\\spam\\eggs' Python

[issue46287] UNC path normalisation issues on Windows

Steve Dower added the comment: My replies to Eryk's comment copied above: Yes, always more tests :) The behaviour of normpath has always been weird and/or incorrect around invalid UNC paths. For example, on 3.10, normpath("//spam///eggs/..") --> "spam". Originally, the path was a file

[issue46287] UNC path normalisation issues on Windows

New submission from Steve Dower : Taken from https://github.com/python/cpython/pull/30362#issuecomment-1006840632 For Windows, should there be tests for invalid UNC paths such as "//", "//..", "//../..", "//../../..", "//server", "//server/..", and "//server/../.."? This will help to ensure