Create Environment
does not check if .venv
already exists
#20027
Labels
area-environments
Features relating to handling interpreter environments
bug
Issue identified by VS Code Team member as probable bug
Type: Bug
Behaviour
Expected vs. Actual
If
.venv
already exists, ask the user whether they want to stick with it or delete it to create a new one. You can't have multiple environments in the same directory due to being able to only have a singlepyvenv.cfg
file.Steps to reproduce:
.venv
.Create Environment
to create an environment with a different Python version than what.venv
already has.Diagnostic data
python.languageServer
setting: PylanceOutput for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)User Settings
Extension version: 2022.17.12871028
VS Code version: Code - Insiders 1.73.0-insider (7ef8e6b, 2022-10-14T05:17:07.227Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: