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:
- Clone https://github.com/thumbor/thumbor
- Run "Create environment" command
Diagnostic data
- Python version (& distribution if applicable, e.g. Anaconda): 3.12.0
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
- Value of the
python.languageServer setting: Pylance
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
User Settings
venvFolders: "<placeholder>"
languageServer: "Pylance"
experiments
• optInto: ["pythonTestAdapter","regionCommentDiagnostics"]
Extension version: 2023.22.1
VS Code version: Code - Insiders 1.87.0-insider (2af6139, 2024-02-01T23:51:02.394Z)
OS version: Windows_NT x64 10.0.22621
Modes:
System Info
| Item |
Value |
| CPUs |
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 2995) |
| GPU Status |
2d_canvas: enabled
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 |
| Load (avg) |
undefined |
| Memory (System) |
31.71GB (10.39GB free) |
| Process Argv |
--log trace --log ms-python.autopep8=debug --crash-reporter-id 11494669-52ca-4f2c-aa0e-29172189cc8e |
| Screen Reader |
no |
| VM |
0% |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vsc_aa:30263845
vscod805:30301674
vsaa593:30376534
py29gd2263:30784851
c4g48928:30535728
2i9eh265:30646982
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
8082a590:30953407
edj9j583:30943796
fegfb526:30952798
7j2b6412:30951517
bg6jg535:30946824
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.languageServersetting: PylanceOutput for
Pythonin theOutputpanel (View→Output, change the drop-down the upper-right of theOutputpanel toPython)User Settings
Extension version: 2023.22.1
VS Code version: Code - Insiders 1.87.0-insider (2af6139, 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