You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add preexisting environment to environment selection #25441
As a user I would like to be able to generate my local environment for my mono repo in a specific way and to be able to switch around them easily in vscode. For this ticket, let's implement a way for a user to add a preexisting env into python environments.
Details
I have a mono repo with multiple environments: API and Pipelines. I generate each of the .venv/ within the mono repo through poetry. This generates these two envs:
api/.venv
pipelines/.venv
However, I seem to be unable to add them both to the environment selection:
Here you see the pipeline environment.
But when I select a different interpreter, the pipeline environment would disappear.
Ideally, I should be able to add both .venv at the same time so that I can swap them around depending on what part of the codebase I am working on.
Hi! Do you have the python environments extension in use? You can see by the python logo in the sidebar. If not, install that and then add this to your settings "python.useEnvironmentExtension: true". From there you can right click on the parent folder of the venv (like api) and select "add as python project". Doing this should make the venv discoverable.
This is not our desired behavior (to have to do this manual action to discover) but is the current status. Thanks
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.
Activity
eleanorjboyd commentedon Sep 8, 2025
Hi! Do you have the python environments extension in use? You can see by the python logo in the sidebar. If not, install that and then add this to your settings "python.useEnvironmentExtension: true". From there you can right click on the parent folder of the venv (like api) and select "add as python project". Doing this should make the venv discoverable.
This is not our desired behavior (to have to do this manual action to discover) but is the current status. Thanks
github-actions commentedon Oct 9, 2025
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.
Happy Coding!