Support micromamba

[DonJayamanne]

Challenges

• Finding the install folder (there are different ways to install this, homebrew, scripts, etc)
• Perhaps safest and easiest way is to spawn micromamba process and then report that manager

Notes:

• We could easily add a different crate to just discover micromamba manager.
• Environments should get discovered provided they are logged in environments.txt
• We can look for the variable MAMBA_ROOT_PREFIX

Probably a debt task.
@karthiknadig /cc

[corneliusroemer]

I came here to ask about micromamba support. Great to see it's already on your list! I just installed VS Code 1.91 and I noticed that the "Python 3.1" errors have disappeared. And there even seems to be micromamba support?

I get this in VS Code 1.91:

[karthiknadig]

@corneliusroemer This is not yet integrated into python extension. I am currently working on that. But, you should be able to see exactly what this finds in Output > Python Locator. It currently runs in parallel to existing discovery code, and logs the results.

[corneliusroemer]

Excellent! In any case, things are already really really good now in 1.91, it's fixed the annoying misrecognition of functioning Pythons as version 3.1.

Great job!

Here's what I see in the locator, looks all good to me, but I might misunderstand what this tool here does:

[DonJayamanne]

Here's what I see in the locator, looks all good to me, but I might misunderstand what this tool here does:

Not sure what you mean.
The logs merely show what was discovered, in above logs they are 4 different Python environments.
I am 100% certain that the envs miniwdl and pango3116 are conda envs.
Not sure about the first and the last item. Are they not conda environments,
i.e. are these the items you are confused about?

[vttrifonov]

i come here from #24812 so my original issues was with micromamba. so i am happy to see that attention is paid to micromamba to make it automagically work in vscode (like conda does). that being said i will be fine to have something even simpler:

1. i will be fine as a start if there is a setting which i can configure by hand that contains folder(s) with environments, e.g. ~/.conda/envs, ~/.micromamba/envs, etc. this can be a global, user, and workspace setting

2. as i explained in the #24812 my biggest issues was not that i had to configure by hand but that even though i kept selecting the correct environment for jupyter, vscode kept "forgeting" my selection. so i am forced to do this again and again... a small suggestion here is to "remember" (across vscode runs) the environments chosen within a project and include those in the kernel/interpreter selection box.

not sure if this belongs in this micromamba discussion but thought i will give you a perspective which can be helpful and might be easier to implement.