-
Notifications
You must be signed in to change notification settings - Fork 300
address np printoptions pre/post v1.22 #4486
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
Conversation
trexfeathers
left a comment
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.
I have confirmed for myself that this will fix the #4480 failures, and I think I understand what's going on! I just had one comment about avoiding a private import.
pp-mo
left a comment
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.
Good enough for now, as noted in comments.
|
Thanks @pp-mo and @trexfeathers 🍻 🥳 💯 There was a lot of history and tech debt associated with this one. Hopefully it's raised the priority on us committing to resolving #3048 and moving away from what we have at the moment 👍 |
🚀 Pull Request
Description
This PR addresses the test failures within #4480 when updating to the latest
numpyv1.22.0.We've now dropped support within
irisforpy37(#4481) but we still require to supportnumpy>= v1.19 (NEP29 Support Table). However numpy/numpy#19686 introduced a change that impactsiris.util.format_arraydue to our use of the internalnumpy.core.arrayprint._formatArrayfunction.This PR maintains our continuing
numpyv1.13 legacy array printing format forpy38andnumpy>= 1.19.As a separate concern, it would be wise to commit to addressing #3048, by at least bumping to the more recent
numpyv1.21 legacy array printing.Consult Iris pull request check list