Message416489
> Hmm..., I get it, but Im not gonna lie it's pretty confusing given
> that in other places `//` works as a substitute for `/`. Maybe it
> should be mentioned in the documentation?
In Linux, the system resolves "//" as just "/". In other POSIX systems, such as Cygwin or MSYS2 (running in Windows), "//" is a UNC path of the form "//server/share/filepath". I would expect resolve() to handle this. For example:
Linux:
>>> p = pathlib.Path('//tmp')
>>> p
PosixPath('//tmp')
>>> p.resolve()
PosixPath('/tmp')
However, resolve() is broken for a UNC path in 3.9 under MSYS2:
>>> p = pathlib.Path('//localhost/C$/temp')
>>> p.exists()
True
>>> p.resolve()
PosixPath('/localhost/C$/temp')
>>> p.resolve().exists()
False
realpath() is also broken for this case in 3.9 under MSYS2:
>>> os.path.realpath(p)
'/localhost/C$/temp' |
|
Date |
User |
Action |
Args |
2022-04-01 14:26:55 | eryksun | set | recipients:
+ eryksun, arhadthedev, John15321 |
2022-04-01 14:26:55 | eryksun | set | messageid: <1648823215.53.0.311335853672.issue47161@roundup.psfhosted.org> |
2022-04-01 14:26:55 | eryksun | link | issue47161 messages |
2022-04-01 14:26:55 | eryksun | create | |
|