Reactivating Terminal

[karthiknadig]

When activating python extension, you see "Reactivating Terminal" in the status bar, and it does not go away.

Workaround:

• Add the following to your User settings.json, and Reload VS Code:

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

• If that does not resolve the issue, try running this command from the command palette: Python: Clear cache and reload.
• If that does not resolve the issue, try setting python.locator to js.

[RMvirtual]

Your workaround does technically get the "Reactivating terminals" loop to stop, but it does not solve the problem of the Python extension failing to be used.

[karthiknadig]

@RMvirtual Please create a new bug and provide details on what is happening. Include logs from Output > Python, and Output > Python Locator. Include your settings as well.

[LukeLIN-web]

Same problem, my python extension cannot work
I tried

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

This workaround does technically get the "Reactivating terminals" loop to stop, but it does not solve the problem of the Python extension failing to be used.

How to setting python.locator to js? I find it in setting dashboard.

Good, setting python.locator to js solve my problem, I can reset my env now.

[aantora]

Hello can you please elaborate on the "

• Add the following to your User settings.json, and Reload VS Code:

  "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"]
  " part? I don't know how to do this, I am a new coder. Thank you.

[karthiknadig]

@aantora You can use the settings UI to find that:

Click on the link that says "edit in settings.json", paste the above line at the end:

As for the python.locator you can find it in settings as well:

[tommyvct]

This problem, however on macOS, does not appear to be happening as frequently as on Windows.

Maybe it have something to do with the difference with zsh and pwsh.

[KuRRe8]

Thanks! It really works. Before the solution, the python locator finds "C:\Program Files\Python39\python.exe" and failed for every new python file. That path is unavailable for many years on my computer, and I tried my best to clean up registry, vscode user database, vscode settings ... but no effect. My mistake was that I didn't immediately remember to come to the official repo issue to search for relative threads.