Add support for micromamba environments

[CarlAndersson]

Type: Bug

Behaviour

Expected vs. Actual

I expect the python: conda path setting to be used everywhere conda is called.
As can be seen from the logs, a plain conda call is used many times, and something tries to find python installations under ~\Miniconda3\..., which does not exist.
This results in that no environments are found, and pylance cannot find locally installed packages.

Steps to reproduce:

1. Uninstall conda if you have it.
2. Install micromamba
3. Set the conda path to point to micromamba

Diagnostic data

• Python version (& distribution if applicable, e.g. Anaconda): 3.11.0
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
• Value of the python.languageServer setting: Pylance

Output for Python in the Output panel

User Settings

condaPath: "C:\Users\carl4189\micromamba\condabin\micromamba.bat"

languageServer: "Pylance"

linting
• flake8Args: "<placeholder>"
• flake8Enabled: true
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: true
• pydocstyleEnabled: true

terminal
• activateEnvironment: false

Extension version: 2023.5.10791008
VS Code version: Code 1.76.2 (ee2b180d582a7f601fa6ecfdad8d9fd269ab1884, 2023-03-14T17:55:54.936Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8 x 2112)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	undefined
Memory (System)	15.78GB (6.73GB free)
Process Argv
Screen Reader	no
VM	0%

[karrtikr]

Thanks for the bug report! We just wanted to quickly acknowledge we received it and we will triage this as soon as we can.

[psobolewskiPhD]

Would love to see this work. Mamba works, because conda is still present. But micromamba doesn't have a base env with conda.

[karrtikr]

Turning this into a feature request as we currently don't support micromamba, to resolve this we need to support identifying micromamba version correctly.

Currently if version is below 4.7, we do not use conda/micromamba run, so environment is not activated before it is used leading to import errors.

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[CarlAndersson]

micromamba run exists at least in micromamba version 1.0.0. The changelog indicates that is has existed since version 0.21.0.
The output from conda info --json and micromamba info --json might be a good place to find out if the command is conda or mircomamba without resorting to inspecting the command name. E.g., conda info --json has a 'conda_version', while micromamba info --json has a 'micromamba version'.
Let me know if there's anything more I can do to assist!

[brettcannon]

Thank you to everyone who upvoted this issue! Since the community showed interest in this feature request we will leave this issue open as something to consider implementing at some point in the future.

We do encourage people to continue 👍 the first/opening comment as it helps us prioritize our work based on what the community seems to want the most.