-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for Python 3.9 #406
base: main
Are you sure you want to change the base?
Conversation
It does not appear possible to use Python 3.13 using our maximum supported Astropy version. I don't think it's worth trying to understand why; we have no mandate to support 3.13 yet. So instead I have explicitly dropped support for Python 3.13+ in I have also regenerated our lock file ( |
8d4c4df
to
1c408fa
Compare
@@ -95,7 +91,7 @@ cov = "pytest --cov-report=xml --cov-config=pyproject.toml --cov=src/dysh --cov= | |||
|
|||
# Run tests across all supported version of Python | |||
[[tool.hatch.envs.test.matrix]] | |||
python = ["39", "310", "311", "312"] | |||
python = ["310", "311", "312", "313"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should 313 be removed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think something got reverted during the rebase onto main. Will look tomorrow
specutils has dropped support for Python 3.9. So, we will do the same
Note that per this spec, https://scientific-python.org/specs/spec-0000/ , we should drop support for Python 3.10 as of Q4 2024 (now). But I don't see any good reason for doing that, as it isn't really adding any maintenance burden and I haven't heard anyone clamoring for new 3.10+ specific features yet