Python Debugger Console unexpectedly added conda dirs to PATH

[fireattack]

I have both native python and conda installed on my computer, but I deliberately does not add conda's python dir to path since I rarely use it.

>where python
C:\Users\ikena\AppData\Local\Programs\Python\Python311\python.exe
C:\Users\ikena\AppData\Local\Programs\Python\Python310\python.exe
C:\Users\ikena\AppData\Local\Microsoft\WindowsApps\python.exe   

And my default Python interpreter (both global and for the workspace) is the C:\Users\ikena\AppData\Local\Programs\Python\Python311\python.exe one, not conda:

However, I noticed that after I ran debugger (either F5 or Ctrl+F5), while debugger indeed uses the correct Python interpreter executable, the created "Python Debugger Console" terminal will somehow has the modified %path%, where a bunch of anaconda3 paths were added:

Left: my default %path%; right: the %path% in "Python Debugger Console"

This is quite annoying as if I want to run some quick python commands in this console sometimes, it ends using the wrong python:

Version: 1.101.2 (user setup)
Commit: 2901c5ac6db8a986a5666c3af51ff804d05af0d4
Date: 2025-06-24T20:27:15.391Z
Electron: 35.5.1
ElectronBuildId: 11727614
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.19045

[eleanorjboyd]

Hi! To confirm this only happens for debug and not for run generally? And you don't have these other conda paths saved anywhere in a setting correct?

[fireattack]

@eleanorjboyd hi, thanks for looking into this.

It will happen in any "Python Debug Console" terminal window/session that is automatically populated by run "Start Debugging" or "Run without Debugging".

I've tried my best to check/toggle my settings and I can confirm I don't have these paths anywhere in my settings.json.
But if there are other places I should look at, feel free to let me know.

[ApexLiberta]

@fireattack

can u check python.terminal.activateEnvironment is causing this issue?

[fireattack]

Setting "python.terminal.activateEnvironment": false does not fix the issue.