Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The conda-libmamba-solver documentation seems out-of-date (now that mamba is the default solver)? #516

Closed
2 tasks done
jypeter opened this issue Aug 28, 2024 · 1 comment · Fixed by #517
Closed
2 tasks done
Labels
source::community catch-all for issues filed by community members type::documentation request for improved documentation

Comments

@jypeter
Copy link

jypeter commented Aug 28, 2024

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

I have read the conda-libmamba-solver main User's guide page, and it feels really weird and confusing, now that libmamba is the default solver in recent installations

For instance, I have an up-to-date version of conda (and related packages): 24.7

> conda list conda
# packages in environment at /home/share/unix_files/cdat/miniconda3_2024-03:
#
# Name                    Version                   Build  Channel
conda                     24.7.1          py312h7900ff3_0    conda-forge
conda-content-trust       0.2.0              pyhd8ed1ab_0    conda-forge
conda-libmamba-solver     24.7.0             pyhd8ed1ab_0    conda-forge
conda-package-handling    2.3.0              pyh7900ff3_0    conda-forge
conda-package-streaming   0.10.0             pyhd8ed1ab_0    conda-forge
conda-which               0.2.0              pyhd8ed1ab_0    conda-forge

And limamba is the default solver since conda 23.9

Yet the user's guide seems to be written for people who still use old versions (e.g. Update from the experimental versions (22.9 and below))

And the tip at the bottom of the page (If you are unsure what configuration is being used by conda, you can inspect it with conda config --show-sources) make no sense for users having a recent version. In my case, I get

 > conda config --show-sources
==> /home/users/jypeter/.condarc <==
channel_priority: strict
channels:
  - conda-forge
  - defaults

I have to use conda info or conda config --show if I want to get the solver information

> conda info | grep solver
                 solver : libmamba (default)
             user-agent : conda/24.7.1 requests/2.32.3 CPython/3.12.3 Linux/3.10.0-1160.108.1.el7.x86_64 centos/7.9.2009 glibc/2.17 solver/libmamba conda-libmamba-solver/24.7.0 libmambapy/1.5.8

> conda config --show | \grep solver
sat_solver: pycosat
solver: libmamba
solver_ignore_timestamps: False

Maybe the page should have different sections, based on the conda version? Or dealing with older versions should go to the FAQ ?

  • if you have conda >= 23.9
  • if you have 22.11 (?) <= conda < 23.9
  • if you have very old versions of conda (conda <= 22.11 ?) : just install mamba directly and use it as a replacement of conda. I maintain a legacy installation based on conda 4.9.2 where I hase succesfully used mamba for a long time

Additional Context

No response

@jypeter jypeter added the type::documentation request for improved documentation label Aug 28, 2024
@travishathaway travishathaway added the source::community catch-all for issues filed by community members label Aug 28, 2024
@jezdez jezdez transferred this issue from conda/conda Aug 28, 2024
@jaimergp
Copy link
Contributor

Thanks, yes, this suggestion is spot on. I'll push a PR shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
source::community catch-all for issues filed by community members type::documentation request for improved documentation
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants