-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
failing tests with pandas 2.1 #8125
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
Comments
To me it looks like |
The doctest works for me locally, investigating package differences in the environment now. Update: OK, it does run, but I get a different result (after to_stacked_array): MultiIndex([('a', 0),
('a', 1),
('a', 2),
('b', nan)],
name='z') instead of MultiIndex([('a', 0.0),
('a', 1.0),
('a', 2.0),
('b', nan)],
name='z') |
I think the doctest failure is unrelated to the removal of - ... coords=[("x", ["a", "b"]), ("y", [0, 1, 2])],
+ ... coords=[("x", ["a", "b"]), ("y", [0., 1, 2])], in xarray/xarray/core/dataarray.py Line 2893 in 1043a9e
|
I've opened pandas-dev/pandas#54920 upstream for the |
Upstream is already working on a fix for the fill_value-issue: pandas-dev/pandas#54927 |
Reopening until doc-test is fixed. |
There are also two pandas-related warnings when building the docs, which cause a "failure" for PR builds on RTD:
Not sure how to (temporarily) fix those, though. |
Thanks (sorry this was an auto-close by GH, I hadn't meant to have it closed) |
No worries @max-sixty, that just happens. It would be great, if we could fine grain closing issues. :-) |
remaining things tracked in #8146 |
What happened?
See #8101
and this doctest
@pydata/xarray can someone take a look please?
The text was updated successfully, but these errors were encountered: