Type: Bug
Behaviour
Expected vs. Actual
Expected: Pressing the hotkey for "Run Python File in Terminal" runs the Python file in the terminal.
Actual: Get a message that says "command 'python.execInTerminal' not found" and nothing else happens.
Steps to reproduce:
- Press the hotkey for "Run Python File in Terminal".
Note that right-clicking the source, then choosing "Run Python > Run Python File in Terminal", appears to do nothing (no error message).
Also note that this used to work fine until recently.
Also note that this issue sounds exactly like #21610 but
- nuking the entire VS Code installation, including extensions, and then reinstalling everything is drastic and tedious
- uninstalling just the Python-related extensions and reinstalling them, as suggested in a Stack Overflow comment, did not work
- issuing the
Python: Clear cache and reload window, as suggested in the closed GitHub issue, also did not work
- even after taking the nuclear option, it only worked for a short while; a day or so later the issue came back
Potentially relevant to point 4: It's on a work laptop that I use both at home and in the office; in between I put the computer to sleep.
Diagnostic data
- Python version (& distribution if applicable, e.g. Anaconda): 3.10.11
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): MicrosoftStore
- 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)
User Settings
languageServer: "Pylance"
terminal
• executeInFileDir: "<placeholder>"
Extension version: 2023.20.0
VS Code version: Code 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d, 2023-11-01T11:29:04.398Z)
OS version: Windows_NT x64 10.0.22621
Modes:
System Info
| Item |
Value |
| CPUs |
Intel(R) Core(TM) i5-10310U CPU @ 1.70GHz (8 x 2208) |
| 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) |
undefined |
| Memory (System) |
7.77GB (0.82GB free) |
| Process Argv |
|
| Screen Reader |
no |
| VM |
0% |
Type: Bug
Behaviour
Expected vs. Actual
Expected: Pressing the hotkey for "Run Python File in Terminal" runs the Python file in the terminal.
Actual: Get a message that says "command 'python.execInTerminal' not found" and nothing else happens.
Steps to reproduce:
Note that right-clicking the source, then choosing "Run Python > Run Python File in Terminal", appears to do nothing (no error message).
Also note that this used to work fine until recently.
Also note that this issue sounds exactly like #21610 but
Python: Clear cache and reload window, as suggested in the closed GitHub issue, also did not workPotentially relevant to point 4: It's on a work laptop that I use both at home and in the office; in between I put the computer to sleep.
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.20.0
VS Code version: Code 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d, 2023-11-01T11:29:04.398Z)
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled