-
Notifications
You must be signed in to change notification settings - Fork 36
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
Require Python 3.8+. #715
Require Python 3.8+. #715
Conversation
Some features such as the HDF5 integration require additional packages. | ||
Supported Python and NumPy versions are determined according to the `NEP 29 deprecation policy <https://numpy.org/neps/nep-0029-deprecation_policy.html>`_. | ||
The signac framework uses the `NEP 29 deprecation policy <https://numpy.org/neps/nep-0029-deprecation_policy.html>`__ as a guideline for when to drop support for Python and NumPy versions, and does not guarantee support beyond the versions recommended in that proposal. |
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.
If this language is approved, I will update signac-flow and signac-dashboard accordingly. Related conversation: #685 (comment)
Codecov Report
@@ Coverage Diff @@
## master #715 +/- ##
==========================================
- Coverage 78.54% 78.51% -0.03%
==========================================
Files 65 65
Lines 7141 7141
Branches 1565 1565
==========================================
- Hits 5609 5607 -2
Misses 1228 1228
- Partials 304 306 +2
Continue to review full report at Codecov.
|
Co-authored-by: Carl Simon Adorf <[email protected]>
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.
Looks solid to me
Description
NEP 29 has dropped support for Python < 3.8. This PR updates signac to require Python 3.8+. This will help with some current work for signac 2.0 where we would like to use newer language/library features.
In the meantime, I caught a problem where our Windows tests were using Python 3.7 instead of Python 3.8 as we intended. Since Python 3.7 is no longer supported, I updated it to Python 3.10 (the latest release at the time of writing) so that it would be running a supported version further into the future.
Checklist: