Can you print your $PATH (or whatever the equivalent of this variable is on Windows), in the integrated terminal? I am experiencing a similar problem (on macOS) and I noticed there are some broken characters in the $PATH, causing the shell to fail in finding the correct python interpreter.

Not sure if this is related, but when python.terminal.activateEnvironment is active, the environment is not loaded correctly. I see some : being parsed as \x3a when I echo $PATH and other variables. This also means, when the virtual environment is active by default (using this extension) I cannot find deactivate command as one of the : in the $PATH has been replaced to \x3a.

@SiddharthPatel45 the \x3a is not caused by Python extension but is a regression in core VS Code: microsoft/vscode#248468

Thanks for the update. Let me follow up on that issue.

I am experiencing this under Windows WSL2. Here's my terminal when trying to run unicorn:

(my_project) username@User-PC:~/code/my_project$ uvicorn src.main:app --reload
Command 'uvicorn' not found, but can be installed with:
sudo apt install uvicorn
(my_project) username@User-PC:~/code/my_project$

There are two solutions to these I personally use:

1. wsl --shutdown since I thought this was the WSL problem and this actually works.
2. A quick swap from venv python to global and back via the bottom right corner environment button.

The moment I do that the command proceeds as expected:

(my_project) username@User-PC:~/code/my_project$ uvicorn src.main:app --reload
INFO: Will watch for changes in these directories: ['/home/username/code/my_project']
INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
INFO: Started reloader process [5474] using WatchFiles
INFO: Started server process [5476]
INFO: Waiting for application startup.

Oh as for the \x3a fix I didn't check that, if you fixed it in the 1.100.2 then great but I've already edited my str variable to not read : from the environment variable but add it in the python app on runtime with f-string.

@maratnugmanov This might have been caused by microsoft/vscode#248468 , can you try updating to VS Code version 1.100.2?

@karthiknadig that was on 1.100.2 I manually go through clicking Check for Update to be sure I'm on the latest stable. So it is still there. Ii will try tomorrow again but this on the latest, that has dropped today.

UPDATE: If that helps, trying to deactivate venv doesn't deactivate it, I'll check what it says later but basically it's like I'm not in venv so nothing to deactivate. So the venv prefix stays and the problem is too.

@karthiknadig yes it's indeed true for 1.100.2, I have tried again today.

(my_project) username@User-PC:~/code/my_project$ uvicorn src.main:app --reload
Command 'uvicorn' not found, but can be installed with:
sudo apt install uvicorn
(my_project) username@User-PC:~/code/my_project$ deactivate
deactivate: command not found
(my_project) username@User-PC:~/code/my_project$ which pip
/usr/bin/pip
(my_project) username@User-PC:~/code/my_project$ which python3
/usr/bin/python3
(my_project) username@User-PC:~/code/my_project$ .venv/bin/activate
bash: .venv/bin/activate: Permission denied
(my_project) username@User-PC:~/code/my_project$
(my_project) username@User-PC:~/code/my_project$ cd .venv/lib/python3.12/site-packages/uvicorn
(my_project) username@User-PC:~/code/my_project/.venv/lib/python3.12/site-packages/uvicorn$

@anthonykim1 can you take a look at this.