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?

Oh, I wasn't aware we did this, thanks for pointing it out !
I note however that daily cron jobs are not picking up numpy 2.0.0b1 at the moment (someone else from the stack of dependencies we're grabbing must be pinning it ?), so right now it might still have some value to add a job just for numpy 2.0. That being said, I should also note that, when I opened this PR yesterday, I thought I was seeing another regression when testing locally against numpy maintenance/2.0.x, but it turned out to be a different problem which had nothing to do with numpy, so there's also less of a need for this job than I previously thought.

Anyway, I propose we re-assess on what to do with this PR on Monday, and maybe by then we'll even see an actual release candidate ?

We could also just add this to the integration testing repo?

Sure ! where's that ?

Ah, right. It is at https://github.com/astropy/astropy-integration-testing

I kicked off https://github.com/astropy/astropy-integration-testing/actions/runs/8512968778/job/23315688712 but since we pinned numpy<2 for astropy v6.0.1 and we do not yet have astropy v6.1rc, it is not picking up numpy 2.0rc. FYI.

since we pinned numpy<2 for astropy v6.0.1 and we do not yet have astropy v6.1rc, it is not picking up numpy 2.0rc.

2.0.0rc1 actually still matches <2, but as I said in #16249 (comment), something else in the env must be pinning it harder (possibly scipy). Anyway, it looks like we're already doing everything we can on our side and there don't seem to be actual hidden incompatibilities to catch any more so let's just close this for now. Thank you both !