-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: MultiIndex.unique losing ea dtype #48335
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
# Conflicts: # doc/source/whatsnew/v1.6.0.rst
midx = MultiIndex.from_arrays([a, b], names=["a", "b"]) | ||
result = midx.unique() | ||
|
||
a = Series([1, 2, NA], dtype="Int64") |
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.
nitpick, can you avoid 1-letter variable names
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, thx. Stupid copy paste miss
cc @mroeschke for a second set of eyes |
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
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.the MultiIndex.unique code path is casting the values to tuples and runs through unique1d. This is really slow.