Skip to content

EXP: split astropy into astropy-core and astropy metapackage - #149

Open
astrofrog wants to merge 2 commits into
mainfrom
astropy-core-and-metapackage
Open

EXP: split astropy into astropy-core and astropy metapackage#149
astrofrog wants to merge 2 commits into
mainfrom
astropy-core-and-metapackage

Conversation

@astrofrog

@astrofrog astrofrog commented Mar 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner

Internal PR to my own fork as just an experiment and to share with a couple of people.

This is to try out https://rind.readthedocs.io to see if we can easily rename astropy to astropy-core and have astropy be a metapackage that installs astropy-core[recommended]. It is an alternative to the kind of approach in PEP 771. The motivations in there are the same and essentially boil down to the fact that

pip install astropy

should give the set-up for the typical user, but there should be a way to do minimal installs too:

pip install astropy-core

This adjusts the publish workflow to show how we can build the metapackage at the same time.

@github-actions

github-actions Bot commented Mar 2, 2026

Copy link
Copy Markdown

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@astrofrog
astrofrog force-pushed the astropy-core-and-metapackage branch from 609c145 to 7d976c8 Compare March 2, 2026 15:01
@astrofrog
astrofrog force-pushed the astropy-core-and-metapackage branch from 7d976c8 to aa04129 Compare March 2, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@astrofrog