Repository navigation
Creating a new venv replaces selection #507
Description
Activity
Then when I add the
testsfolder as a project it assigns a global Python rather than one of the virtual envs. This seems like a bug since it should probably default to a virtual env but it would be great if we could be smarter about this selection to auto to the environment that matches a req file if presentOk one more weird update I reloaded and then it selected the devenv for both projects
Observed this feedback in user studies as well, users did not expect the environment to be automatically selected unless the option made it more clear this was "Create and Select" they imagined it would just create the environment
Opted to enforce just "create" so this will no longer override existing selections. If we get user feedback we can switch to a "Create and Select" flow
- added a commit that references this issue
on Jun 16, 2025 - added a commit that references this issue
on Oct 23, 2025 - locked as resolved and limited conversation to collaborators
on May 2, 2026
I currently only have the root as a project with a virtual env already created and selected. I created a new virtual environment for
dev-requirements.txtprior to adding the tests folder as a project and the new virtual environment is now selected for the root. Should we replace a virtual environment with a virtual environment?