-
Notifications
You must be signed in to change notification settings - Fork 89
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
Jedi ignores current virtualenv? #345
Comments
What does the full traceback in Looks like the server has three
One of those is the one that you are mentioning, the other two come elsewhere. The first step I would suggest is to try disabling |
The two other virtual envs are set by myself in my config, but for the first one I don't know where it's coming from? |
Like I said, try disabling Also, issue title is a bit confusing as I'm not sure which virtualenv do you consider "ignored" in this situation. |
Not sure if this will help but after encountering this error I found that I could solve it by installing the stable version of Elpy which was providing the EPC server. |
I resolved this by first removing ;; set the correct virtualenv path (current one)
(setq jedi:environment-virtualenv
(list (shell-command-to-string "which python"))) I believe this avoids hard-coding the virtualenv path in the config file. |
Goto-definition didn't work if the word was in a different file. Somehow
Following this I went ahead and cloned the emacs-jedi repo and installed it with |
Jedi setup
Error (jedi):
I don't understand why I always have this argument even if I have (setq jedi:server-args '("--virtual-env" "/home/n214/.virtualenvs/env1") in my config
The text was updated successfully, but these errors were encountered: