New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calling Path.exists() on non-existent drive raises WindowsError #47
Comments
No idea... I do note that standard python has precisely same implementation for the import pathlib
pathlib.Path(r"E:\Whatever\blah.txt").exists() gives the same error? If so (and I expect it will), then you'll need to take this upstream. |
Ah, you're right. This is an upstream issue. I'm seeing the same behavior with |
Ok. When it gets fixed there, the fix should land back here as well with the next upstream sync. |
Sounds good. I've gone ahead and created an issue upstream in the python tracker https://bugs.python.org/issue35692 |
This includes a fix for issue #47.
The fix is now in develop, and will be included with the next release. It should work now, if not, do let me know and I'll look into it. Thanks once more for engaging with upstream to get this addressed! |
Any idea why this is happening?
I tested this with version 2.3.2 and the latest commit 87f9a0e
The text was updated successfully, but these errors were encountered: