-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Fix difference functionality for Period Indexes #59148
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
Conversation
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.
lgtm @mroeschke @jbrockmendel any concerns?
def _difference(self, other, sort=None) -> PeriodIndex: | ||
if isinstance(other, Index) and other.inferred_type == "string": | ||
try: | ||
other = other.astype(self.dtype) |
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.
I don’t think we do this type of casting in general. In fact, I’d expect the private _difference to only be reached with matching dtypes
tm.assert_index_equal(idx_diff, expected) | ||
|
||
idx_diff = other.difference(index, sort) | ||
expected = pd.Index([]) |
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.
No, the difference should be the entire ‘other’
Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen. |
Index.difference
is returning too many values #58971doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.