-
Notifications
You must be signed in to change notification settings - Fork 219
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
Recommend mambaforge + mamba in the installation instructions and contributing guides #2368
Comments
Yes, I think we should recommend miniconda or micromamba. IMO we should also recommend mamba for contributors in https://www.pygmt.org/latest/contributing.html#setting-up-your-environment, since the conda solver can get tedious with the number of development dependencies that we have. |
I agree.
micromamba is not a good option, because (https://mamba.readthedocs.io/en/latest/user_guide/micromamba.html):
|
Related thread at https://discourse.pangeo.io/t/mamba-mature-enough/3154/4 on how |
Sounds great. mambaforge + mamba is the way to go. |
Kinda unrelated, but I just found out about https://prefix.dev/blog/online_environment_solving today and was playing with solving a PyGMT development environment (conda-lock.yml file) at https://prefix.dev/envs/weiji14/pygmt. This is today's resolved environment at https://prefix.dev/envs/weiji14/pygmt/285fy5jawbs0, installable using It's still a very young project built by the P.S. Couldn't get |
In the installation instructions, we recommend using Anaconda:
Here is a comparison between Anaconda and miniconda: https://stackoverflow.com/a/45421527.
From my own experience, Anaconda packages too many packages by default, which causes slow installation, large disk spaces and potential package conflicts.
I wonder if we should recommend miniconda instead.
The text was updated successfully, but these errors were encountered: