-
Notifications
You must be signed in to change notification settings - Fork 663
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
Increase minimum numpy version to 1.21 #3983
Conversation
Codecov ReportBase: 93.50% // Head: 93.50% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## develop #3983 +/- ##
========================================
Coverage 93.50% 93.50%
========================================
Files 190 190
Lines 24943 24943
Branches 3523 3523
========================================
Hits 23322 23322
Misses 1100 1100
Partials 521 521
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I think that might be fine now, I'm not a typing expert though so I'm heavily relying on mypy to tell me if I'm wrong (also I've only made changes where it was indicated in |
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.
Quick question.
reference_positions: np.ndarray = reference # type: ignore | ||
configuration_positions: np.ndarray = configuration # type: ignore | ||
reference_positions: npt.NDArray = reference # type: ignore | ||
configuration_positions: npt.NDArray = configuration # type: ignore |
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.
Do we want to have subtyping on eg npt.NDArray[np.float32]
?
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.
Unsure, but I'd probably ask that this get punted to a separate issue (unless these changes lessen the quality of typing from what it used to be)?
I'd prefer not move the goalpost here from "bumping up our numpy requirements" to "incidentally dealing with a ton of typing issues"
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.
Yep totally fair. I'll raise an issue once merged. The typing here is improvement for sure, it can just be more stringent but agree its a separate issue.
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.
No expert on all the places CI needs changing but the use of the new typing looks good.
Note fixes #3748 |
As per NEP29, the 2.5.0 release of MDA will happen ~ March 2023 and will be Python 3.8+ & NumPy 1.21+
See: https://numpy.org/neps/nep-0029-deprecation_policy.html#support-table
Changes made in this Pull Request:
PR Checklist