-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: drop_duplicates raising for boolean arrow dtype with missing values #54670
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/v2.1.0.rst
@@ -249,3 +249,10 @@ def test_drop_duplicates_ignore_index(self): | |||
result = ser.drop_duplicates(ignore_index=True) | |||
expected = Series([1, 2, 3]) | |||
tm.assert_series_equal(result, expected) | |||
|
|||
def test_duplicated_arrow_dtype(keep): |
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.
Did you intend to parameterize over keep
?
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.
Nope, that was a lesson that you shouldn't copy paste without double checking
Since Arrow support isn't new anymore I suppose we shouldn't be backporting bug fixes as aggressively anymore, but I would still be okay with it |
Ok then maybe lets backport low risk fixes and decide on the others on a case by case basis |
…n arrow dtype with missing values
Thanks @phofl |
…boolean arrow dtype with missing values) (#54692) Backport PR #54670: BUG: drop_duplicates raising for boolean arrow dtype with missing values Co-authored-by: Patrick Hoefler <[email protected]>
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.cc @mroeschke
More generally, how do we want to proceed with Arrow EA fixes after 2.1 is out?