-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Fix for 14674: better check for integer pixel dimensions #14676
Conversation
Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.
|
This isn't making tests pass because there are other parts of the codebase that cause the same deprecation warning. See https://github.com/astropy/astropy/actions/runs/4768953830/jobs/8478846216?pr=14676. @pllim What would you like to do here? Maybe we could ignore the deprecation warning globally, but add an explicit check for it just in this module? Or would it be better just to integrate this PR into another one handling this warning everywhere? |
Wow, that is crazy. Were we abusing numpy that badly?! |
caused by numpy/numpy#10615 |
@saimn , what do you think? Should we blanket ignore or try to fix the 50+ failures before v5.3rc? |
I already had a PR for this: #14671 |
@larrybradley , you plan to fix all of them? 👀 |
Not today! |
I plan to do the rc end of next week so we have a bit of time. It's not critical since it's only Numpy dev but Numpy 1.25 is expected in June I guess so we will need to fix errors soon anyway. |
Closing in favor of #14671 |
This is a minor change to fix a future deprecation warning id'd in #14764. The logic to be checked is: is the range a whole number?
xref #14674