-
Notifications
You must be signed in to change notification settings - Fork 60
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
Allow numpy 1.24. #563
Allow numpy 1.24. #563
Conversation
The SHA256 failures here are related to a recent change in the skimage 0.19 seems to not handle this properly. It downloads the new version, but compares it with the old hash value. skimage 0.20 downloads the older version so the old hash value check passes. for upcoming skimage 0.21 it will download the new version and pass with the new hash value. Two possible workarounds for cuCIM are: |
Great. Once #564 is merged, feel free to update this PR with |
Due to a [recent change in the eagle image](https://gitlab.com/scikit-image/data/-/merge_requests/22) used in one of our test cases, skimage 0.19 fails to load it. As a solution, we can just restrict this one test to run only for `scikit-image>=0.20`. Should resolve test failures seen in #563 Authors: - Gregory Lee (https://github.com/grlee77) Approvers: - Bradley Dice (https://github.com/bdice) - https://github.com/jakirkham URL: #564
/merge |
Thanks all! 🙏 |
This removes the upper bound on
numpy<1.24
to allow newer NumPy versions.