-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Automatically select interpreter when VIRTUAL_ENV is set #2124
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
You might have just gone above my head a little; I don't really understand the difference. But it does appear to be the case that it's not quite accurate, at least not in the cases that a user would recognize. Namely, when I put in place my goofy hack from the latest comment at #2333, it all "Just Works" the way I expect/think it should. It seems to me like re-activating a detected virtualenv in ~/.bash_profile wouldn't work so effectively if what you're saying is true. Does that make any sense? |
I get it, but I think we might be talking about different things in terms of how/where code is being executed. |
Closing as dup of #18178. |
When a virtual environment is activated the
VIRTUAL_ENV
environment variable is set to the location of the virtual environment. We could pick up on this and use it as the implicit value ofpython.pythonPath
when that setting has not already been set.The text was updated successfully, but these errors were encountered: