mne-tools
We may soon be able to drop all mamba-related info from our install docs
Proposed documentation enhancement
The mamba solver will become the default solver for conda soon, hence no need for ordinary users to explicitly touch mamba anymore:
The upcoming, special 23.10.0 release will be dedicated to the switch of the default solver to libmamba.
https://github.com/conda/conda/releases/tag/23.9.0
It will be nice to purge that language! I think we should still say something like "if you have problems with the "solving environment" step failing or being slow, make sure you're on conda version 23.10.0 or newer".
The mamba CLI is / will be deprecated as the solver is now fully integrated into conda. See this PR:
https://github.com/mamba-org/mamba/pull/3054
This means that we should recommend users install "conda >=23.10" and remove all references to mamba from the docs.
conda 23.10 was released on Oct 30
For CI, we should switch from Mambaforge to Miniforge.
cc @larsoner @cbrnr
The mamba CLI is / will be deprecated as the solver is now fully integrated into conda. See this PR:
That's not quite what is happening. Mamba is still a first class citizen. What is happening is mamba.py which was glue between conda and libmamba has been removed in favor of a full C++ CLI client.
@AntoinePrv since the Micromamba CLI is not compatible with Mamba, we are in fact deprecating Mamba.
I think what you call "mamba.py" in your comment is typically called "Mamba", and what you call "Mamba" is typically called "libmamba". IMO we should stick to the following terminology:
- Mamba: The Conda-compatible Python CLI that will be deprecated.
- Micromamba: The C++ binary based on libmamba.
- libmamba: The C++ library.
- libmambapy: The Python binding to the C++ library.
With this terminology, "Mamba" will be deprecated.
Yes this is what I meant! The mamba binary is deprecated. The mamba solver library (libmamba) and micromamba binary are not. Thanks for the clarification, @jonashaag
Yes, except that we will ship a mamba executable that uses the same code as micromama in mamba-forge like-container. The executable name and user experience will remain.
Anyhow, this is very much WIP and the details are not settled...
Yes, except that we will ship a
mambaexecutable that uses the same code asmicromamainmamba-forgelike-container. The executable name and user experience will remain.
"uses the same code" as in "a conda-compatible frontend" or the same code as in "ln -s micromamba mamba"?
@0xbe7a as in ln -s micromamba mamba (and micromamba is a conda-compatible frontend, we are interested in pairing any reported missing feature)
