You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've was redirected from the Python Language Server Repo (Here you have the issue that I've created in there: microsoft/python-language-server#1731)
I just copy and pasted what I've just wrote there:
If I use the Go To Definition function with a module that it is inside an egg/zip file, I'm getting the following error:
Unable to open 'test.py': Unable to read file (Unknown (FileSystemError): Error: ENOTDIR: not a directory, stat '/home/users/alberto/testEnv/testPackage-py2.7.egg/myProject/foo/test.py').
I can import that file without problems within a Python Terminal by:
from myProject.foo import test
If you need more info, please, let me know! :)
Thanks!
Apparently, the problem is that CentOS is not treating the zips files as folder (like Microsoft Windows does), so if I try to use the any of the Intellisense feature (like Go To Definition) in a file that is pointing to another file inside a zip (or egg) file, VSCode gave the error that I typed above.
I'm wondering if there is any way to handle this.
Thanks!
Does this issue occur when all extensions are disabled?: Yes/No
The text was updated successfully, but these errors were encountered:
Steps to Reproduce:
Hello!
I've was redirected from the Python Language Server Repo (Here you have the issue that I've created in there: microsoft/python-language-server#1731)
I just copy and pasted what I've just wrote there:
Apparently, the problem is that CentOS is not treating the zips files as folder (like Microsoft Windows does), so if I try to use the any of the Intellisense feature (like Go To Definition) in a file that is pointing to another file inside a zip (or egg) file, VSCode gave the error that I typed above.
I'm wondering if there is any way to handle this.
Thanks!
Does this issue occur when all extensions are disabled?: Yes/No
The text was updated successfully, but these errors were encountered: