Add support python interpreter from micromamba

[Wongboo]

I used python interpreter from system, conda, mamba and micromamba. The extension detects python from first three sources correctly, but fails to detect python from micromamba.
micromamba uses $MAMBA_ROOT_PREFIX the same way as mamba, but locates in ~/micromamba by default. So its python interpreter locates in $MAMBA_ROOT_PREFIX/envs/**/bin/python.
Also when using a env from micromamba, since the env does not necessarily contains conda. So

conda activate env_name

should be replaced by

micromamba activate env_name

[karrtikr]

While we don't officially support it yet, you could set "python.condaPath" setting to "micromamba" and it should work for most use cases. To discover the env automatically, look into python.venvPath setting.

[Wongboo]

While we don't officially support it yet, you could set "python.condaPath" setting to "micromamba" and it should work for most use cases. To discover the env automatically, look into python.venvPath setting.

It seems that this does no help.

[GarrisonD]

I have the same problem. When I set python.condaPath to /usr/local/bin/micromamba, VS Code is trying this when I create a new terminal:

> source /usr/local/bin/activate /opt/conda/envs/my-env

bash: /usr/local/bin/activate: No such file or directory

Python extension output:

2023-07-22 11:01:52.460 [info] > /usr/local/bin/micromamba info --json
2023-07-22 11:01:52.845 [info] Send text to terminal: source /usr/local/bin/activate /opt/conda/envs/my-env

[karrtikr]

Closing in favor of #20919 as something to consider implementing at some point in the future. We do encourage people to continue 👍 the first/opening comment there as it helps us prioritize our work based on what the community seems to want the most.