Repository navigation
python.defaultInterpreterPath #25778
Description
Type: Bug
python.defaultInterpreterPath：:"${workspaceFolder}/venv/Scripts/python.exe"
but agent python commod don‘t use defaultInterpreterPath
Extension version: 0.31.5
VS Code version: Code 1.104.1 (0f0d87fa9e96c856c5212fc86db137ac0d783365, 2025-09-17T23:36:24.973Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (4 x 3292) |
| GPU Status | 2d_canvas: enabled 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 trees_in_viz: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 11.90GB (2.52GB free) |
| Process Argv | . --crash-reporter-id 7e8c0fea-0f91-429b-9af5-7605ce876021 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
9hi5e907:31436603
aj953862:31281341
6abeh943:31336334
cloudbuttont:31379625
3efgi100_wstrepl:31403338
use-responses-api:31390855
je187915:31401257
ec5jj548:31422691
cp_cls_t_966_ss:31454198
cp_cls_c_1081:31454833
nes-jmp-himalia-001:31437105
nes-set-to-on:31441941
Activity
vs-code-engineering commentedon Feb 1, 2026
Thanks for creating this issue! It looks like you may be using an old version of VS Code; the latest stable release is 1.108.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
eleanorjboyd commentedon Feb 10, 2026
what do you mean by "agent python"? I also made substantial changes to how defaultInterpreterPath is handled last week. Could you try it again on the pre-release version of the python environments extension?
eevmanu commentedon Mar 5, 2026
myoraclesix this seems related to #25190 (comment)
github-actions commentedon Apr 5, 2026
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
myoraclesix, you can help us out by closing this issue if the problem no longer exists, or adding more information.
sdg002 commentedon Apr 21, 2026
I am experiencing this issue myself. VS Code refuses to honour the
defaultInterpreterPathin the settings.json and jumps to a different Virtual environment was being used by another VS Code project on a completely different repository.The inconsistency/instability of VS Code with respect to Python interpreter selection makes me feel insecure. I have to always remember to manually select the interpreter path every time I open this repository.
VS Code verison
Version: 1.116.0 (user setup)
Commit: 560a9dba96f961efea7b1612916f89e5d5d4d679
Date: 2026-04-15T00:28:13Z
Electron: 39.8.7
ElectronBuildId: 13797146
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22631
settings.json
{ "git.ignoreLimitWarning": true, "editor.formatOnSave": true, "pylint.args": [ "--disable=C0116", "--disable=W1203", "--disable=C0301", "--disable=C0114", "--disable=W1309", ], "python.defaultInterpreterPath": "${workspaceFolder}/.venv/Scripts/python.exe", "python.terminal.activateEnvironment": true }extensions.json
{ // Recommended VS Code extensions for this workspace "recommendations": [ "ms-python.python", "ms-python.vscode-pylance", "ms-python.autopep8", "ms-python.debugpy", ], "unwantedRecommendations": [ "ms-python.vscode-python-envs" ] }github-actions commentedon May 21, 2026
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
myoraclesix, you can help us out by closing this issue if the problem no longer exists, or adding more information.
sdg002 commentedon May 25, 2026
Works for me - but I have disabled the Python Environments extension
ms-python.vscode-python-envs.github-actions commentedon Jun 24, 2026
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
myoraclesix, you can help us out by closing this issue if the problem no longer exists, or adding more information.
github-actions commentedon Jul 25, 2026
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!