-
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
Test multiroot support for terminal activation using environment variables #21102
Comments
Hi @karrtikr, great work here. I have just been testing the fix. I opened two workspace folders into which I placed a python file each and selected different interpreters for each. I created two terminals per workspace folder. When I change the interpreter for one of the folders, one of the terminal labels becomes yellow, but not the second one, despite them being associated to the same folder. Upon clicking on the Screen.Recording.2023-04-25.at.11.40.15.mov |
@aiday-mar Thanks for identifying this! it does look like either a limitation of the API or a bug.
|
Refs: #21101
Complexity: 5
Create Issue
Requirements
Similar to #20884 hence preassigning. Make sure to check the (new) requirements.
PATH
during installation.conda init
to initialize the shell.conda config --set auto_activate_base False
.conda create -n <name> python -y
.python -m venv <name>
to create virtual envs.Verification
Use a workspace with multiple workspace folders. (
File -> Add folder to workspace...
)For each workspace folder:
Python: Select Interpreter
command. This should be different for each folder.Open multiple terminals for each workspace folder:

For each workspace folder,
w
:w
is activated using the selected environment forw
. Run the following in terminal:.venv
created viapython -m venv .venv
it looks something like:Python
has a description for which env is activated next to it:Python: Select Interpreter
command, a warning sign should appear to the right of terminal with new env changes that're about to be made:Click show environment contributions highlighted above, make sure the environment variables are for the right environment:
The text was updated successfully, but these errors were encountered: