realpath(..., strict=ALLOW_MISSING) can unexpectedly succeed on Windows #135122
Labels
3.13
bugs and security fixes
3.14
bugs and security fixes
3.15
new features, bugs and security fixes
extension-modules
C modules in the Modules dir
OS-windows
type-bug
An unexpected behavior, bug, or error
Comments
|
Thanks for the catch! I'd call that a bug (but not a security issue). |
|
At least, such "gotcha" could be documented. I don't know whether we can detect and change this behavior, or leave it as a Windows peculiarity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Bug report
In new tests added for #117562 I noticed that
os.path.realpath('file1/file2', strict=os.path.ALLOW_MISSING)returns'file1/file2'when filefile1exist on Windows.On Posix you will get NotADirectoryError here, but Windows raises ALLOW_MISSING if the intermediate path is a file instead of directory, and it will be ignored with ALLOW_MISSING.
It is expected that if
realpath(..., strict=ALLOW_MISSING)does not fail, you can simply create intermediate directories or the final file/directory. At least on Posix. But on Windows it will always fail, because there is already a file here.cc @encukou
The text was updated successfully, but these errors were encountered: