![]() ![]() If necessary, you can go back to using the classic solver without modifying your conda installation: ![]() ![]() If that’s not the case, please consider submitting a bug report or feature request in the conda-libmamba-solver repository. If the new solver is not working as you expect:Ĭheck if the behavior you are observing is a known issue or a deliberate change. ![]() What can I do if this update doesn’t work for me? As soon as these installers are updated to contain conda 23.10.0 or later, they will automatically default to using the conda-libmamba-solver plugin. Since July 2023, the conda-libmamba-solver plugin has been included in all major conda ecosystem installers (miniforge, miniconda, mambaforge and Anaconda Distribution), but was disabled by default. To address growth-related challenges within the conda ecosystem, the conda maintainers, alongside partners Anaconda, Quansight and QuantStack, introduced a new conda dependency solver based on the Mamba project in December 2022. In short: to make conda faster and more accurate.Ī “solver” is the core component of most package managers it calculates which dependencies (and which version of those dependencies) to install when a user requests to install a package from a package repository. The previously “classic” solver is based on pycosat/ Picosat and will remain part of conda for the foreseeable future, a fallback is possible and available. This is an announcement about an important change in conda’s functionality: With this 23.10.0 release we are changing the default solver of conda to conda-libmamba-solver! □ □ This information is drawn from the GitHub conda projectĬhangelog: 23.10.0 () ✨ Special announcement ✨ ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |