Skip to content
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 python 3.7 #365

Merged
merged 1 commit into from
Mar 15, 2024
Merged

drop python 3.7 #365

merged 1 commit into from
Mar 15, 2024

Conversation

jhauschild
Copy link
Member

@Jakob-Unfried is there any other file which I need to update to drop python 3.7?

@jhauschild jhauschild added this to the Release 0.99 milestone Mar 14, 2024
@Jakob-Unfried
Copy link
Member

Pretty sure thats everything.
Why do we need to drop it?
I like doing it, I am just curious.

@jhauschild
Copy link
Member Author

No particular reason, it's just that python 3.7 has reached it's end of life, so I don't want to worry about supporting it any more, and don't think the tests need to run on python 3.7 anymore, saving resources in the github actions.

I think we can also remove our restrictions on numpy>=1.13 and scipy>=0.18, which are effectively enforced by the ABI pinning of compatible numpy anyways.

@jhauschild jhauschild merged commit faa0f27 into main Mar 15, 2024
9 checks passed
@jhauschild jhauschild deleted the drop_python_3_7 branch March 15, 2024 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants