-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
vscode's Python extension does not load the right python interpreter from pyenv #7029
Comments
@vict0rsch, thanks for letting us know about this. I have some questions:
Thanks! |
Hi,
|
@vict0rsch, thanks for the info. We'll work on figuring out what's going on. Also, when you click on the Python version on the left side of the status bar you should get the list of recognized interpreters. Do all of the ones listed by |
hmmm for some reason now it shows up. I have not updated anything. Maybe some cache entry got changed? So now I still have the issue of the terminal quitting instantly as it is opened: Error says:
But I don't understand what, in vscode's python extension, triggers this |
How are you launching the terminal? Also, from the screenshot (in the status bar) it looks like you have a system Python activated (selected), rather than a "pyenv" Python. Make sure the interpreter in the status bar has "(pyenv)" in it. As to the command, "source activate.sh" is used when you have a virtual environment (e.g. venv, virtualenv) is active. For pyenv we do "pyenv shell". Your active Python environment appears to be neither, so it isn't clear what is going on. |
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off. |
Environment data
Expected behaviour
The default python interpreter is
~/.pyenv/shims/python
When I run
which python
in my terminal I do get~/.pyenv/shims/python
.python --version
does return the expected3.7.4
Actual behaviour
The interpreter suggests that
~/.pyenv/shims/python
is actually3.6.4
. Maybe this also causes a mismatch and this pyenv crash I getLogs
None
Output from
Console
under theDeveloper Tools
panel, on selecting the interpreterThe text was updated successfully, but these errors were encountered: