DEP: drop support for Python 3.10#16903
Conversation
|
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.
|
|
👋 Thank you for your draft pull request! Do you know that you can use |
8d71ea2 to
f25d6a9
Compare
mhvk
left a comment
There was a problem hiding this comment.
This looks all good to me! Approving though second set of eyes on the CI changes would be very helpful.
|
I also revived changes from #16680 (re: #16680 (comment)) |
|
One more thing: I just checked and you ended up removing all actual usage of |
|
Good point, let's clean that up while we're at it. I'll keep the |
7246a53 to
c21d784
Compare
|
might as well undraft this now |
|
Oh no, another conflict. Can you please rebase again? Thanks! |
and sync oldestdeps pins. Also remove other mentions of very old Python versions. Remove ignoring warning in pytest that no longer needs to be ignored. No longer need to specific numpy 2.0.0rc in pins now that stable is out. DOC: Clarify change log a bit more.
that is not needed since Python 3.4. Co-authored-by: Marten van Kerkwijk <mhvk@astro.utoronto.ca>
…e oldest supported numpy
1172050 to
4e5f0ae
Compare
|
rebased ! (I think it's time we merge this) |
|
Re: oldestdeps + alldeps Looks like it came from #12522 (comment) by @saimn . It was a while ago when we do not have so many "optional" dependencies and that PR was to simplify jobs, so this combo was not necessarily to fix some specific problem we had per se. So we can definitely rethink it. See #16950 |
docs/changes/16903.other.rst
Outdated
| @@ -0,0 +1 @@ | |||
| Updated minimum supported Python version to 3.11. As a result, minimum required versions for ``ipython``, ``packaging``, ``pyarrow``, PyYAML, and ``scipy`` were updated as well to be compatible, while ``tomli`` and ``typing_extensions`` are no longer needed. | |||
There was a problem hiding this comment.
As a user I would like optional and mandatory dependencies to be distinguished (we don't need to go into any details beyond that).
There was a problem hiding this comment.
@eerovaher , any suggested wordings? I think everything I added are "optional".
There was a problem hiding this comment.
tomli and typing_extensions were only needed for development, so they should not have been mentioned in the change log at all.
There was a problem hiding this comment.
I plan to follow up on this. Thanks !
|
aarch64 failure unrelated and the daily cron with remote data timeout also unrelated. I am going to modify the change log for Eero the best I can and then merge this before poor Clément have to rebase again. |
|
I updated |
|
Thanks @pllim for all your help ! |
DOC: simplify changelog entry for #16903
Description
I initially just wanted to measure the diff of doing this but ended up doing all (?) the work needed, so might as well open a
draftPR.This would enable:
enum.StrEnumwhere it makes sense, when available #16603FAQ
Q: When is this going to be released?
A: End of 2024. Please see https://github.com/astropy/astropy/wiki/Release-Calendar
Q: Why so soon? Python 3.10 EOL is not till Oct 2026.
A: This is due to https://github.com/astropy/astropy-APEs/blob/main/APE18.rst that follows https://scientific-python.org/specs/spec-0000/ that recommends, "Support for Python versions be dropped 3 years after their initial release."
Subpackage approvals
After merge
Repo admin needs to update branch protection rules for
main.