-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
unpin numpy
#8061
unpin numpy
#8061
Conversation
The doctests CI fails because xarray/xarray/core/variable.py Lines 1870 to 1880 in eceec5f
In this particular case, the fill value itself will never appear in the unstacked array, so we could just use |
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.
These warnings were getting annoying, thanks!
Unrelated, but noticed again: |
We can do that, but note that the only error that's new is
the other ones appear to be
Any idea how to fix those? |
this important because the fix in `numpy` that now means we *don't* need it anymore has been around for less than 3 months (requires a sufficiently new version of `mypy`).
I don't think those are numpys fault. Edit: nevermind, numpy Arrays are not supposed to work and mypy is actually correct here. Your ignore is correct. Somehow the older Mypy did not recognize this. The Hashable None error usually disappears magically when you fix the other errors. |
Yes sry. Saw that too late. You are totally correct |
hah, yeah, I also didn't see your edit soon enough. In any case, that leaves us with the |
I barely know what I'm doing when it comes to typing, but from what I can tell the reason is a |
once tests pass this should be ready for a final review. Edit: see above for the |
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.
LGTM
numbagg
fromconda-forge
#7415It seems in a previous PR I "temporarily" pinned
numpy
to get CI to pass, but then forgot to unpin later and merged it as-is. As a result, we have not been running the main CI withnumpy>=1.24
ever since, even though nownumpy=1.25
has been around for a while.