-
-
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
Make kind
argument in CFTimeIndex._maybe_cast_slice_bound
optional
#5359
Make kind
argument in CFTimeIndex._maybe_cast_slice_bound
optional
#5359
Conversation
Hello @spencerkclark! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-05-22 23:58:02 UTC |
e52aee9
to
591263e
Compare
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.
thanks for the fix, @spencerkclark. The docs should be fixed by indenting the whats-new.rst
entry.
Co-authored-by: keewis <keewis@users.noreply.github.com>
thanks again, @spencerkclark. |
This incorporates an update to handle a pandas deprication issue when using cftime objects. See pydata/xarray#5359
Pandas recently deprecated the
kind
argument inIndex._maybe_cast_slice_bound
, and removed its use in several internal calls: pandas-dev/pandas#41378. This led to some errors in the CFTimeIndex tests in our upstream build. We never made use of it inCFTimeIndex._maybe_cast_slice_bound
so the simplest fix for backwards compatibility seems to be to make it optional for now -- in previous versions of pandas it was required -- and remove it when our minimum version of pandas is at least 1.3.0.pre-commit run --all-files
whats-new.rst