Testing selecting env from source terminal: activate base in terminal confusion

[andreamah]

Testing #20538

When I tried manually activating base and then opening up vscode, the old testLaunch env is activated instead

Nevermind! I was on Case IV, so this expected. But keeping this issue open because I have some concerns in the follow-up comments

[andreamah]

I notice that when I manually deactivate testLaunch and try to re-launch from the command line using case III, it re-activates testLaunch although i was on base before I accept the modal dialog. I know that it should not automatically switch to base, but should it go out of its way to switch away from it?

[karrtikr]

In case III you should not be getting a modal dialog, so I'm a little confused. Are you sure that's the case you're referring to?

[andreamah]

I was just re-checking this case and I think I was getting mixed up again 😅 I think I had set the conda environment from the interpreter before trying case III (and this was a case w/o a modal), so that's why it was switching back. I think it's expected.