Skip to content
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

Unable to open a file within an egg/zip file in the editor #83779

Closed
asierralozano opened this issue Oct 31, 2019 · 1 comment
Closed

Unable to open a file within an egg/zip file in the editor #83779

asierralozano opened this issue Oct 31, 2019 · 1 comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@asierralozano
Copy link

asierralozano commented Oct 31, 2019

  • VSCode Version: 1.39.2
  • OS Version: CentOS 7

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:

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

@mjbvz
Copy link
Collaborator

mjbvz commented Oct 31, 2019

Duplicate of #75559

@mjbvz mjbvz marked this as a duplicate of #75559 Oct 31, 2019
@mjbvz mjbvz closed this as completed Oct 31, 2019
@mjbvz mjbvz added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 31, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants