What about conda version > 4.4.0 on Powershell or Command Prompt?
Don't we need to make any changes?

Else, please create a separate issue for that.

I was not aware of any changes relative to powershell. I'll take a look.

We need to consider all shells.
We have a case statement in the class, and we need to ensure all are satisfied.
I.e. works on:

• Windows + Linux + Mac
• Powershell, Powershell core, bash, tcsh, zsh, fsh, etc..

From what I can tell, activation on powershell has not changed. When I get a chance, I'll verify on Windows.

Everything worked fine when activating a selected env on 4.4.0+.

Please ensure you have tested this PR.
This is not the solution what was discussed, this is what failed for me.

The solution that was discussed was (documented it in the issue): #1882 (comment)

Right, and @brettcannon expressed reservations about working around the "init" step under 4.4.0+. Let's get together today and iron this out.

the conda instructions such that "conda" is on their $PATH.

This is what we would like to avoid. In fact conda will NOT be in their PATH.
Thats why we introduced a setting for condaPath in settings.json.

I talked with @brettcannon about this. He does not want the extension to initialize conda (under 4.4.0+) if the user has not followed conda's instructions; the error message given by the conda command (if it is absolute or otherwise on $PATH) will explain what the user needs to do.

Do you mean we should help users if conda is installed but they did not follow conda's instructions to put it on their $PATH? In that case they will get a relatively unhelpful error message: conda: command not found. FWIW, the same goes for pre-4.4.0 (i.e. source activate): -bash: activate: No such file or directory.

FWIW, the same goes for pre-4.4.0

Pre-4.4.0, conda (root env) was in the current path, hence this worked.