Type: Bug
Behaviour
Expected vs. Actual
I have the .venv file in the project's root so the extention opens automatically the virtual enviroment as Python interpreter every time I open vscode.
But after the update of the vscode server in WSL this is not happening anymore. Even if I try to do it manully from the extension Python: Select Interpreter option selecting the .venv/bin/activate.
Note: I'm using pyenv and poetry to create the .venv dir. The virtual env is created when I execute poetry install but the problem arise after the update of vscode server.
Steps to reproduce:
- Start vscode
- Select Python: Select Interpreter
Diagnostic data
- Python version (& distribution if applicable, e.g. Anaconda):
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Unknown
- Value of the
python.languageServer setting: Default
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Experiment 'pythonPromptNewToolsExtNonExistantcf' is active
LSP Notebooks experiment is enabled
LSP Notebooks interactive window support is enabled
> conda info --json
> poetry env list --full-path
cwd: .
> ~/.pyenv/versions/3.10.10/bin/python -I ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
> ./.venv/bin/activate -I ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
[ERROR 2023-2-11 2:10:47.807]: [Error: Command failed: /home/standardio/repos/drfbackend-example/.venv/bin/activate -I /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
/bin/sh: 1: /home/standardio/repos/drfbackend-example/.venv/bin/activate: Permission denied
at ChildProcess.exithandler (node:child_process:399:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Socket.<anonymous> (node:internal/child_process:451:11)
at Socket.emit (node:events:526:28)
at Pipe.<anonymous> (node:net:687:12)] {
killed: false,
code: 126,
signal: null,
cmd: '/home/standardio/repos/drfbackend-example/.venv/bin/activate -I /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py'
}
> ./.venv/bin/python -I ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
> ~/.pyenv/versions/3.11.2/bin/python -I ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
> /bin/python3 -I ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
> /usr/bin/python3 -I ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
> ./.venv/bin/activate -I ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
[ERROR 2023-2-11 2:10:49.824]: [Error: Command failed: /home/standardio/repos/drfbackend-example/.venv/bin/activate -I /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py
/bin/sh: 1: /home/standardio/repos/drfbackend-example/.venv/bin/activate: Permission denied
at ChildProcess.exithandler (node:child_process:399:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Socket.<anonymous> (node:internal/child_process:451:11)
at Socket.emit (node:events:526:28)
at Pipe.<anonymous> (node:net:687:12)] {
killed: false,
code: 126,
signal: null,
cmd: '/home/standardio/repos/drfbackend-example/.venv/bin/activate -I /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/get_output_via_markers.py /home/standardio/.vscode-server/extensions/ms-python.python-2023.4.1/pythonFiles/interpreterInfo.py'
}
Starting Pylance language server.
User Settings
languageServer: "Pylance"
formatting
• provider: "black"
Extension version: 2023.4.1
VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2
System Info
| Item |
Value |
| CPUs |
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592) |
| GPU Status |
2d_canvas: enabled 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 |
| Load (avg) |
undefined |
| Memory (System) |
15.86GB (6.87GB free) |
| Process Argv |
--folder-uri=vscode-remote://wsl+Ubuntu/home/standardio/repos/drfbackend-example --remote=wsl+Ubuntu --crash-reporter-id 8d335ee9-e2d1-4e37-839e-2fe4c1947e27 |
| Screen Reader |
no |
| VM |
0% |
| Item |
Value |
| Remote |
WSL: Ubuntu |
| OS |
Linux x64 5.15.90.1-microsoft-standard-WSL2 |
| CPUs |
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592) |
| Memory (System) |
7.69GB (6.70GB free) |
| VM |
0% |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewvextcfv2:30681851
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1:30587005
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
vsctsb:30677850
funwalk2cf:30682975
Type: Bug
Behaviour
Expected vs. Actual
I have the .venv file in the project's root so the extention opens automatically the virtual enviroment as Python interpreter every time I open vscode.
But after the update of the vscode server in WSL this is not happening anymore. Even if I try to do it manully from the extension
Python: Select Interpreteroption selecting the .venv/bin/activate.Note: I'm using pyenv and poetry to create the
.venvdir. The virtual env is created when I executepoetry installbut the problem arise after the update of vscode server.Steps to reproduce:
Diagnostic data
python.languageServersetting: DefaultOutput for
Pythonin theOutputpanel (View→Output, change the drop-down the upper-right of theOutputpanel toPython)User Settings
Extension version: 2023.4.1
VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2
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