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.

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

Note that I do not recommend we add a test job for the backport branch, as the release candidate is expected any day now and would be easier to test against. I also assume that this kind of failures should be rare enough that it's not worth checking for them systematically. However, running the test suite locally will be part of my morning routine until we see numpy 2.0.0rc1 😄

Looks like this went under everyone's radar yesterday. @mhvk can you review this please ?

Would it be possible, in a separate PR, to add numpy 2.0 to our workflows?

I'm planning to do it when rc1 gets out. Possibly earlier if it takes more than a couple days from now.

I'm planning to do it when rc1 gets out. Possibly earlier if it takes more than a couple days from now.

Sounds good!