forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugneeds PRReady to be worked onReady to be worked onverifiedVerification succeededVerification succeeded
Milestone
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.
Metadata
Metadata
Assignees
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugneeds PRReady to be worked onReady to be worked onverifiedVerification succeededVerification succeeded