Repository navigation
Prompt users if they already have a .venv #19894
Description
Testing #19883
I already have a .venv in my project. I was curious what would happen if I went through the Python: Create Environment steps again. I can't tell if anything happened. Should we prompt users if they already have a .venv, allowing them to choose to override it or back out of creating a new .venv and just use the existing one? The Dev Containers extension works similarly: if a user chooses the command to add a dev container config and they already have one, they're asked if they'd like to override or just use the existing one.
Activity
karrtikr commentedon Oct 3, 2022
Karthik Nadig (@karthiknadig) Try using
vscode-python/src/client/interpreter/configuration/interpreterSelector/commands/setInterpreter.ts
Line 138 in 870ae8f
karrtikr commentedon Oct 3, 2022
We should probably mention in the prompt and the logs that we just selected the existing
.venvin the workspace.karthiknadig commentedon Oct 3, 2022
Temporary resolution here is that we auto-select the existing environment for now, as the intended users of this command are beginners. This is done.
If we see that people are getting confused by auto-selection, we can provide bit more clarification. For
venvthere is no way to override other than deleting and re-creating, so we will defer that for now.For issues mentioned by Kartik Raj (@karrtikr) I have created separate bugs.
Fix bugs found during TPI (#19925)
Fix bugs found during TPI (microsoft#19925)
Fix bugs found during TPI (microsoft/vscode-python#19925)