-
Notifications
You must be signed in to change notification settings - Fork 35
Remove support for Python 3.7 #802
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
Comments
Seems quite early to drop 3.7 tbh - is there much to be gained? To me there aren't any standout features in 3.8 making it worthwhile, and we're unlikely to (shouldn't?) depend on features required numpy 1.22 for a long time. I don't feel strongly about it, though. |
No particular rush, just wanted to open it for discussion. Installing Python 3.8 envs using conda is easy enough on most platforms so I suspect that shouldn't be a blocker. |
Well that was quick. Our upstream tests just failed because xarray has already dropped Python 3.7. |
Pandas 1.4.0 does not support Python 3.7. |
The build is now failing on Python 3.7 (https://github.com/pystatgen/sgkit/actions/runs/3186604485), so I'm thinking it's probably time to remove support for it. |
No point in swimming against the tide I guess. |
NumPy 1.22 no longer supports Python 3.7, so we should consider removing support for it in the next release of sgkit.
This would be consistent with https://numpy.org/neps/nep-0029-deprecation_policy.html, which says Python 3.7 can be dropped from Dec 26, 2021.
The text was updated successfully, but these errors were encountered: