Change mention of conda (was: change conda to miniforge) #617
Conversation
There was a problem hiding this comment.
astropy/astropy#16555 was superseded by astropy/astropy#16987 and I don't see any usage of miniforge install over there.
Never mind my comment, the install page indeed ditched miniconda for miniforge, so the actual conda command is ru from the right place. And it's just an unfortunate side effect that the commands look the same but the configs are different. So, my comment for this section would be to fully get rid of it; and only point to the install guide in the docs as there isn't enough space to go into the nuances between |
as suggested by bsipocz
pllim
changed the title
| <p/><pre>pip install astropy[recommended] --upgrade</pre> | ||
| If instead you normally use <code>conda</code>, you can do: | ||
| <p/><pre>conda install -c conda-forge astropy</pre> | ||
| or using <code>update</code> instead of <code>install</code> if <code>astropy</code> is already installed. | ||
| The astropy core package is also available in a number of other package managers, so be sure to check your preferred one! |
There was a problem hiding this comment.
What is the status of "other package managers"? Is this now just Debian-based linux package managers? AFAIK we no longer support any Mac package managers.
There was a problem hiding this comment.
Once in a while, we get issues from random distros (e.g., astropy/astropy#14166) so they are out there even if we might not be aware.
Co-authored-by: Tom Aldcroft <[email protected]>
pllim
changed the title
|
Thanks for the review, @taldcroft ! I accepted all your suggestions. |
This is really just a companion to astropy/astropy#16555 to synchronize what's on the web site with whatever that settles on. Please have discussion about what we should actually recommend in astropy/astropy#16555 so that we don't spread it around multiple threads.
Rendered doc: https://output.circle-artifacts.com/output/job/fc974b2f-31be-45e0-a824-116fb2da9647/artifacts/0/html/index.html