-
-
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
⚠️ Nightly upstream-dev CI failed ⚠️: pandas
removed deprecated keyword arguments
#7266
Comments
Looks to be a result of https://github.com/pandas-dev/pandas/pull/49101/files Seems like we have to change to |
Yes, I think so too. I can look into it more this weekend. Clearly we need to change the code that relies on pandas immediately. For resampling with a |
We also still have #6985 open. Maybe we should try to catch Deprecation warnings in the nightly builds and raise an error / Automatic issue, so we can fix things before they break. |
I went ahead and actually implemented the
I agree -- something like that would be useful in general. In this particular case it seems like we were aware of it at one point, but just lost track after silencing it initially for compatibility reasons (#4292 (comment)). Unfortunately that means that this was silenced in user code as well. |
maybe we can extend the action / create a new one to open one issue per unique deprecation message. However, for that we'd need to log the warnings in the |
pandas
removed deprecated keyword arguments
we've got a few more errors now:
I've renamed this issue to allow tracking more recent failures in new issues. |
Should we add some sort of deprecation warning regarding the use of the (I did not end up restoring the pandas warning in #7284) |
That would be nice. It seems like we could also just do it in a later release? |
Sorry I didn't get to adding the warning today. I'll try and put something together over the weekend so that it gets into the release after today's. I'm not sure exactly when pandas 2.0 will be out, but regardless I guess at least it could still be valuable for anyone who doesn't upgrade xarray and pandas at the same time. |
As I think about this more, it wouldn't be too hard for us to support the Maybe you were already thinking along those lines @dcherian. |
closed by #7444 |
Workflow Run URL
Python 3.10 Test Summary
The text was updated successfully, but these errors were encountered: