Open new "Python" when executing using different Python environment

[xxc-zsz]

When I select the venv environment and execute the script, the terminal will display the name of the current virtual environment. At this time, I switch to the conda virtual environment and execute the script again. The terminal has not changed. It can be seen from the command that the interpreter environment has been switched, but the name displayed in front of the directory has not changed.

Unless I manually open a new terminal, a new virtual environment is activated.

Related questions in SO.

[karrtikr]

Thanks for reporting, we can confirm the issue.

[eleanorjboyd]

Hi there! 👋

Thanks again for reporting this issue. Based on what you described, this appears to touch the same parts of our environment/activation logic that we’ve recently replaced in our new Python Environments extension. A lot of the behavior in this area now follows a completely different activation and environment-resolution path, so this may already be fixed.

We’d really appreciate it if you could try the new extension and let us know—this helps us confirm that the new implementation addresses older issues like yours.

👉 Enable the new extension with "python.useEnvironmentsExtension": true (then you should see a Python icon in the sidebar.
📫 More details on enablement here
📝 Useful background documentation on activation here

If you do run into issues, please include as much info and reproduction steps or the "Report issue..." command inside VS Code!

Thanks again for reporting this originally, and for helping us validate the new environment direction for Python in VS Code 🙌

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!