Repository navigation
Fix cudf.pandas datetimelike plotting failures (canonical freq offsets + Period/offset pickling) #23054
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
Merged
Merged
Fix cudf.pandas datetimelike plotting failures (canonical freq offsets + Period/offset pickling) #23054
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
418afac
fix
galipremsagar 42ca645
Merge branch 'main' into plotting_freq
galipremsagar 6e7f4ce
Merge remote-tracking branch 'upstream/main' into plotting_freq
galipremsagar 8410d2a
fix
galipremsagar 1cf26a3
Store pandas offsets in DatetimeIndex._freq directly
galipremsagar c9cd350
Merge branch 'main' into plotting_freq
galipremsagar d791fe0
Preserve DateOffset n/normalize in serialization and guard freq-less …
galipremsagar fdb05e0
Merge branch 'main' into plotting_freq
galipremsagar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Are we at a stage where we could use
pd.DateOffset(**kwds)directly?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.
Not quite — a generic
pd.DateOffset(days=1)never compares equal to the fast offsets pandas infers (pd.DateOffset(days=1) != pd.offsets.Day()) and itsfreqstris not parseable, which would break freq comparisons and the freq round-trip through_validate_freq/serialization.to_offset(Timedelta(...))is not a substitute either, since it yields<24 * Hours>for a daily delta instead of<Day>. So single-unit offsets still need converting to their fast pandas equivalents via_maybe_as_fast_pandas_offset; I added a comment at the call site in d791fe0 explaining this.