-
Notifications
You must be signed in to change notification settings - Fork 44
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
Problems with Jedi in VS Code #266
Comments
I've got the same issue here microsoft/vscode-python#21265 |
Apparently, this is not only in vscode, but I'm using neovim and algo get the same problem. Completions for builtin libs fine, but for any external package no sign |
Have you activated your virtual environment before opening Vim? I'm using neovim, just tested out completions from a 3rd party package, and things work fine for me. |
Yes, in my setup I use the Mason plugin to install the language servers, and apart from that, I have the virtual environment I work on properly activated, and yet no completions for third part packages |
I have the same issue with VSCode. Enabling verbose mode using sys.argv += ['-v']
sys.exit(cli()) when starting the language server in the vscode extension the messages are printed, and I don't see VSCode passing the environment anywhere
|
Any fix for this? I seem to have similar problem and I have described it in coder/code-server#6619 I hope this can be fixed.. |
I have the same question!!! |
You guys have to help us somehow with what's actually going wrong. It feels like the wrong environment is detected. But why is the wrong environment detected? What is special about your installations? How many Python versions have you installed? Are you using virtualenvs? What is your editor/IDE? Writing "I have the same question!!!" is not helpful at all. If you want us to put in work always think of us as humans, too. Try to put in your absolute best into helping us solve the problem. |
OK,I have solved the problem this afternoon, just download "Pyright" extention from vscode market, it can solve all problems. Because of the consideration of security, I have to use "code-server" to attach the server, but "Pylance" can not be used in code-server. So I have to use jedi, while it seems that it can not detect the virtual conda environment automatically... |
Hi, when I switch to Jedi in VS Code, built in modules are recognised correctly but other modules (for example PyTorch) installed with pip are not.
Details can already be read here.
microsoft/vscode-python#21060 (comment)
Does anyone have an idea what the problem could be?
The text was updated successfully, but these errors were encountered: