Uh oh!
There was an error while loading. Please reload this page.
unpin numpy - #8061
Conversation
keewis
commented
Aug 12, 2023
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 |
headtr1ck
commented
Aug 13, 2023
Unrelated, but noticed again: |
keewis
commented
Aug 13, 2023
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. |
headtr1ck
commented
Aug 13, 2023
Yes sry. Saw that too late. You are totally correct |
keewis
commented
Aug 13, 2023
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 |
numbaggfromconda-forge#7415It seems in a previous PR I "temporarily" pinned
numpyto 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.24ever since, even though nownumpy=1.25has been around for a while.