DOC: What happened to mamba.api?

[HaoZeke]

Troubleshooting docs

• My problem is not solved in the Troubleshooting docs

Anaconda default channels

• I do NOT use the Anaconda default channels (pkgs/* etc.)

How did you install Mamba?

Micromamba

Search tried in issue tracker

mamba.py

Latest version of Mamba

• My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

ASV last year began supporting mamba as a solver through the mamba.api module (here). I see now that it was removed completely on main, last seen as part of v1.5.6. Naturally this means it is not usable anymore without vendoring in the relevant bits of mamba.api.

However, I was wondering if there was a more concrete migration guide / other suggestions.

mamba info / micromamba info

No response

Logs

No response

environment.yml

No response

~/.condarc

No response

[HaoZeke]

I'm also not sure if #3054 is related (perhaps it is for downstream "builders" like asv), though since boa still uses libmambapy that shouldn't affect asv.

[JohanMabille]

In (micro)mamba 2 we decided to drop the mamba python code, to avoid maintaining two parallel equivalent workflows. The Python bindings will still be provided, but they will simply forward the call to the C++ functions already used in micromamba, no more logic will be done on the Python side.

We are progressively progressively porting the missing API to libmambapy, there will be breaking changes and a migration guide will be provided when the APIs are a bit stabler.

EDIT: in the meantime, do not hesitate to report here all the APIs you need and you cannot find in the libmambapy folder.