P. L. Lim

> This should go to 8.0.0 instead, shouldn't it ? The milestone is definitely negotiable. Originally I thought it might be okay to do *pending* deprecation in v7.1 and then...

command.py has been deprecated for 2 years and I don't think anyone is using it... But I can split that into a different PR if turns out we need to...

So, should I move out the `command.py` stuff into a separate PR, or just re-milestone this whole PR to v8? Do you want the pending deprecation in v7.1 or v8?...

OK. I will revert the API removal here. See https://github.com/astropy/astropy/pull/17883

There is no longer API removal in this PR. Linkcheck failure is unrelated.

I remilestoned this to 8.0

@mwcraig approved as well on Slack, so merging. Yeehaw. 🎆

@ejeschke , please let me know if you need help with this. But I want to make sure none of your users somehow still need Python 3.8 before I work...

I think the bumps look reasonable. Thanks for the heads up!

Failures are unrelated.