Run Python File button "command not found" after installing the extension

[leobrqz]

I had the deprecated Python Environments extensions and updated to this new one. Everything was working fine a second before i did this.

When creating a new project, enviroment and opening a new terminal, it properly shows up (.venv) on the terminal.

pip install works fine and goes to the .venv

If i run python main.py on the terminal directly (bash) it works just fine

But, if I tried to run with the button on the top right, it returns this multiple times in a row (like 8-12 times):

D:\Exercises\Python\.venv\Scripts\python.exe d:/Exercises/Python/main.py
bash: D:ExercisesPython.venvScriptspython.exe: command not found

This happens on multiple editors for some reason, even on a completely clean install of VScode

If i try again to run with the button, the error appears just one time, it doesn't spam it again.

More information:

On the settings.json:

    "python.useEnvironmentsExtension": true, # marked as "Unkown" -  I've tried changing to false and restarting, didn't do anything
    "python.defaultInterpreterPath": "c:\\Users\\Conta\\AppData\\Local\\Python\\pythoncore-3.14-64\\python.exe" # Removing it doesn't do anything also

My versions:

python 3.14.0
pip 25.2

[anthonykim1]

What shows up when you select environment extension icon on the left panel?

[leobrqz]

I don't have a screenshot from before, but:

I've managed to to make it work again, but I had to completely uninstall and delete all leftover files from vscode(including projects .vscode and .venvs, ~user/.vscode and Roaming/Code) and also start with a clean profile, without having the deprecated extension before installing the MS one.

What I did different this time was having a clear profile to start and deleting the projects .venvs and leftovers from AppData, which the default uninstallation hadn't removed.

VScode was/is version: 1.108.2

I think the issue can be closed but it was annoying to deal with this mid work and i'm not sure why/what caused it

Screenshot from after fixing:

Note:

On editors like Cursor I couldn't make it work, but I believe it's because it uses a previous build of VScode (?).
The terminal spam doesn't happen on Cursor.

[anthonykim1]

Glad they worked out now, let us know if this starts happening again! You can directly ping me.