You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The installation of the development astropy is different than regular astropy (ie installation of cython required as well as a few other packages). It would be useful to have an easy way to install all the requirements for the developer package via pip or conda.
For example, we could have an astropy-all package that installed all the affiliated packages and an astropy-dev that installed all the requirements to develop astropy.
I somewhat like the idea of astropy-all in the form as it was suggested on the mailing list. However I think there should be a discussion what to include, as including all the affiliated packages in there may be a bit too much. At the moment the are 28 packages listed as affiliated, and this number is growing, which is good. But many of them are very specific for a topic, and I as a user may prefer not to have everything.
From the dev prospective as mentioned in this issue, I don't see much sense in an astropy-all. For core development one doesn't need any of the affiliated packages (let alone all), and for affiliated dev one needs to use the dev version of the given package and not a release, and maybe a few dependencies. However there is a high chance that those dependencies are already there in a dev version.
Activity
bsipocz commentedon May 11, 2016
I somewhat like the idea of
astropy-allin the form as it was suggested on the mailing list. However I think there should be a discussion what to include, as including all the affiliated packages in there may be a bit too much. At the moment the are 28 packages listed as affiliated, and this number is growing, which is good. But many of them are very specific for a topic, and I as a user may prefer not to have everything.From the dev prospective as mentioned in this issue, I don't see much sense in an
astropy-all. For core development one doesn't need any of the affiliated packages (let alone all), and for affiliated dev one needs to use the dev version of the given package and not a release, and maybe a few dependencies. However there is a high chance that those dependencies are already there in a dev version.eteq commentedon May 12, 2016
I do like the idea of
astropy-dev- I frequently find myself conda installing those and wishing for an alias or similar.mwcraig commentedon May 23, 2016
So you can try this, which I'm happy to move over to the astropy conda channel once I figure out how to do that:
conda env create mwcraig/astropy-dev-py3bsipocz commentedon Feb 20, 2019
I think that using
options.extras_requirehas solved this issue, no one can easily install everything with:pip install astropy[all,test,doc]