Environment changed while path is not

[peter-jerry-ye]

I have a multi-root workspace project. It works on code-space : when I spawn a terminal where a virtual environment is created, it would first execute source .venv/bin/activate before anything else.

However, on my local machine, it doesn't work. Even if the environment changes suggest that it has been activated, I'm not seeing it anywhere:

How should I debug to figure out the actual issue?

[karthiknadig]

@peter-jerry-ye Add this to your User settings, and reload VS Code.

    "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"]

[peter-jerry-ye]

Works like a charm. Thank you.

[peter-jerry-ye]

Another question. It work for the terminals I opened, but if I create a task, it's still not working. Do you have any suggestions on that case?

[karthiknadig]

If you want to specify the selected Python interpreter used by the Python extension for tasks.json or launch.json, you can use the ${command:python.interpreterPath} command.

{
  "label": "Run current file",
  "type": "shell",
  "command": "${command:python.interpreterPath}",
  "args": ["${file}"]
}

[peter-jerry-ye]

Thank you for your response. Is there any documents on these parameters, such as python.interpreterPath that you mentioned? Or ways to enable virtual environment (so as to use the installed comamnds from venv instead of executing python directly)?