-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
REGR: Avoid regression warning with ea dtype and assert_index_equal order False #47325
Conversation
left = Index(safe_sort(left)) | ||
right = Index(safe_sort(right)) | ||
left = Index(safe_sort(left), dtype=left.dtype) | ||
right = Index(safe_sort(right), dtype=right.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.
maybe another issue, but the check_names check is later. It maybe that would need to resuse the code pattern you added in #47206. Not here, as this PR is targeted 1.4.3, just an observation.
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.
Good point, I am not using that myself, so I am a bit fuzzy on all the keywords :)
It is actually a bit more comlex, because These calls return regular indexes, even if a MultiIndex was given. I'll open an issue about it
Edit: Sorry misunderstood you. You are correct, we have to use exactly the same pattern
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.
my thinking was that your fix in #47206 looked quite useful to robustly sort indexes. and maybe a safe_sort_index would be handy. (IIRC we cannot support pandas objects in safe_sort but would need to check this). I wonder can the fix in #47206 suffer from the rogue warning too without the dtype specified there?
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.
Yep you are completely right. Opened #47330 for 1.5
doc/source/whatsnew/v1.4.3.rst
Outdated
@@ -24,6 +24,7 @@ Fixed regressions | |||
- Fixed regression in :func:`read_csv` with ``index_col=False`` identifying first row as index names when ``header=None`` (:issue:`46955`) | |||
- Fixed regression in :meth:`.DataFrameGroupBy.agg` when used with list-likes or dict-likes and ``axis=1`` that would give incorrect results; now raises ``NotImplementedError`` (:issue:`46995`) | |||
- Fixed regression in :meth:`DataFrame.resample` and :meth:`DataFrame.rolling` when used with list-likes or dict-likes and ``axis=1`` that would raise an unintuitive error message; now raises ``NotImplementedError`` (:issue:`46904`) | |||
- Fixed regression in :func:`assert_index_equal` when ``check_order=False`` and :class:`Index` has extension dtype (:issue:`47207`) |
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 think I may have been wrong to add the regression label to #47207
Not strictly a regression since 1.3.5 did not have EA backed Indexes and the code sample created an object dtype Index. maybe this should be in the bugfix section. wdyt?
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.
You are correct wrt ea back indexes, but you can also trigger this with
idx1 = pd.Index([1, 3], dtype="object")
idx2 = pd.Index([3, 1], dtype="object")
tm.assert_index_equal(idx1, idx2, check_order=False)
I'll add a test and will adjust the release note
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.
Added both
tm.assert_index_equal(idx1, idx2, check_order=False) | ||
|
||
|
||
def test_assert_index_equal_object_ints_order_false(any_numeric_ea_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.
don't need the fixture otherwise lgtm.
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.
Thx, good point. Removed.
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 @phofl lgtm
thanks @phofl |
…dtype and assert_index_equal order False
@meeseeksdev backport 1.4.x |
Could not push to auto-backport-of-pr-47325-on-1.4.x due to error, aborting. |
@@ -24,6 +24,7 @@ Fixed regressions | |||
- Fixed regression in :func:`read_csv` with ``index_col=False`` identifying first row as index names when ``header=None`` (:issue:`46955`) | |||
- Fixed regression in :meth:`.DataFrameGroupBy.agg` when used with list-likes or dict-likes and ``axis=1`` that would give incorrect results; now raises ``NotImplementedError`` (:issue:`46995`) | |||
- Fixed regression in :meth:`DataFrame.resample` and :meth:`DataFrame.rolling` when used with list-likes or dict-likes and ``axis=1`` that would raise an unintuitive error message; now raises ``NotImplementedError`` (:issue:`46904`) | |||
- Fixed regression in :func:`assert_index_equal` when ``check_order=False`` and :class:`Index` has extension or object dtype (:issue:`47207`) |
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.
@phofl FYI :func:`assert_index_equal`
doesn't render. probably needs to be :func:`testing.assert_index_equal`
.
no need to follow-up as can be done with other cleanups before release.
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, will try to do correctly in the future
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.