Create enviroment fails when there's a .venv file in the workspace #22842
Labels
area-environments
Features relating to handling interpreter environments
author-verification-requested
Issues potentially verifiable by issue author
bug
Issue identified by VS Code Team member as probable bug
needs PR
Ready to be worked on
verification-found
Issue verification failed
Milestone
Type: Bug
Behaviour
Expected vs. Actual
When there's a .venv file in the workspace, the create environment command shows the option to either recreate or use the existing .venv in the workspace. However, it's just a file for fish support, and not an actual environment. Since we don't support naming, it fails to select or create a new environment.
Steps to reproduce:
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: 2023.22.1
VS Code version: Code - Insiders 1.87.0-insider (2af613979f646fc4dcebfeaedc7d14f138c7b072, 2024-02-01T23:51:02.394Z)
OS version: Windows_NT x64 10.0.22621
Modes:
System Info
canvas_oop_rasterization: enabled_on
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_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: