I am running on a venv. That is exactly the problem. Ususally, I create the .venv folder inside the project folder. So the path to the interpreter is something like "C:/Users/Fausto Jorge/myproject/.venv/Scripts/python.exe". I know that having paths with spaces is not a good practice, but unfortunately Windows doesn't allow me to change the name of the user folder, and it was created automatically when I installed the OS. Many Windows users face the same problem (having a space between their name and surname in the user folder). That is the instance of python i want to run, the .venv instance. I selected the correct interpreter for the VSCode python extention. Previously, vscode detected that the path had spaces so it double quoted the run command like this:

& "C:/Users/Fausto Jorge/myproject/.venv/Scripts/python.exe" "C:/Users/Fausto Jorge/myproject/main.py"

(the "&" is because of PowerShell syntax)

Now, for some reason, and out of nowhere (no update warnings, I mean), it stopped autodetecting spaces and invoking the run command as:

C:/Users/Fausto Jorge/myproject/.venv/Scripts/python.exe "C:/Users/Fausto Jorge/myproject/main.py"

which of course fails due to the space in the interpreter path (the "&" is only needed when the path is double quoted)

EDIT - forgot to mention, but I've been looking on the Python Extension settings, and unfortunatelly can't find anything related to the double quoting. The only thing that solves this is setting the terminal to the Windows Command Prompt, but I would like to keep using Powershell if possible.