[issue31842] pathlib: "Incorrect function" during resolve()

Change by Eryk Sun : -- stage: -> needs patch type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue31842] pathlib: "Incorrect function" during resolve()

Eryk Sun added the comment: > perfectly valid redirected paths (winfsp ram drives for example) I mounted a WinFsp MEMFS filesystem on a directory, which set a mountpoint that targets the root path of a volume device in the native "\Device" object directory. It didn't create a volume GUID nam

[issue31842] pathlib: "Incorrect function" during resolve()

Erik Aronesty added the comment: bug is worse than that: perfectly valid redirected paths (winfsp ram drives for example) now break in python 3.9.6 (maybe fixed in later version?) >>> import pathlib >>> p=pathlib.Path('C:\\Users\\erik\\Atakama') >>> p.resolve() Traceback (most recent call l

[issue31842] pathlib: "Incorrect function" during resolve()

_ added the comment: Still happening on Python 3.9.2 on Win10 when using a Ram Drive. Any chance of getting this fixed? -- nosy: +riffitos ___ Python tracker ___

[issue31842] pathlib: "Incorrect function" during resolve()

christopher.pickering added the comment: Hi, is there a status update on this issue? Thanks! -- nosy: +christopherpickering ___ Python tracker ___

[issue31842] pathlib: "Incorrect function" during resolve()

Eryk Sun added the comment: > When strict is "false", pathlib should not fail if the network > share is inaccessible. A redirected filesystem (i.e. a share, whether local or remote) that's physically inaccessible should fail with a FileNotFoundError -- due to underlying errors such as ERROR

[issue31842] pathlib: "Incorrect function" during resolve()

Change by Karthikeyan Singaravelan : -- nosy: +eryksun ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue31842] pathlib: "Incorrect function" during resolve()

LiJiayuan added the comment: Same Error. It happend by resolving a path which is not under C: driver, in Windows System. >>> Path().resolve() Traceback (most recent call last): File "", line 1, in File "C:\Users\zom\scoop\apps\miniconda3\current\envs\web\lib\pathlib.py", line 1159, in r

[issue31842] pathlib: "Incorrect function" during resolve()

maciozo added the comment: Same error occurs when attempting to resolve a path on an ImDisk RAM disk: >>> pathlib.Path("T:\\").resolve() Traceback (most recent call last): File "", line 1, in File "C:\Users\maciozo\AppData\Local\Continuum\miniconda3\envs\brainboxes\lib\pathlib.py", line

[issue31842] pathlib: "Incorrect function" during resolve()

New submission from Erik Aronesty : When strict is "false", pathlib should not fail if the network share is inaccessible. It should, as documented, catch the exception and continue with as much of the path as it has. >>> pathlib.Path("v:").resolve() Traceback (most recent call last): File

[issue31842] pathlib: "Incorrect function" during resolve()

Change by Erik Aronesty : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___ Py