-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Unable to use pytest from mapped network drive #5826
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
Comments
Is this a regression? (i.e. did it work in older versions? (which?)) |
I've not used pytest before, so I'm not sure if this is a regression. |
at first glance this looks like a windows issue of python, as it happens in the resolve method of pathlib |
I get the same issue and for me it worked in previous versions. I git-bisected it and it appears that 6a9bf28 is the first bad commit. Edit: Sorry, wrong reference. Updated. |
Also, agreed that the issue comes from Python on Windows, as |
Another issue related to |
Seems that Python will not change anything and pytest should do the work: https://bugs.python.org/issue37993 resolution: not a bug |
@abhilash1in can you (or another windows user) verify if the issue disappears if |
@Thibuko it seems that the issue that pops up in the python bug also means that pytest has to replace thanks for bringing the python issue to attention |
A similar issue occurs on RAM disks (O:\ in this case):
This behavior seems to be described here: https://bugs.python.org/issue31842 Edit:
|
This will be fixed in pytest 6.0 because we are no longer resolving paths. 👍 |
Running
pyest --version
using PowerShell displays the pytest version when I'm in my home directory or any other local directory on my Windows machine. When Icd
into a mapped network drive (Q:\
) and runpyest --version
, I getPermissionError: [WinError 5] Access is denied: '.'
. I get the same error when I runpyest --version
inside as well as outside a virtual environment when I'm in a mapped network drive.pip list
from the virtual environment you are usingThe text was updated successfully, but these errors were encountered: