Incompatible Python environment could be auto-activated in ROS terminal

I have ms-python.python extension installed and it by default will automatically launch a Python environment for every terminal open in VSCode, and which results in unexpected behaviors. Any thought?

[seanyen]

Sourcing c:\opt\ros\melodic\x64\setup.bat does the trick to make c:\opt\python27amd64\python.exe on the list. And I need to manually switch to it once to make the change happen in workspace settings.json.

[kejxu]

No, a virtualenv is chosen instead.

I think this might be the reason, as the Python extension detects that the interpreter is from venv, it will attempt to activate the environment in the terminal

And here are the choices I have. Do I need to source c:\opt\ros\melodic\setup.bat before running vscode?

Yes, I think so. our (ros) python install path needs to be in the environment so that the extension can pick it up. Maybe you could also try typing that in manually, I think that would also work.

I am guessing it’s because I have gone through this earlier, so when I launch a vscode instance without sourcing setup.bat first, I can still see the (ros) python: