-
-
Notifications
You must be signed in to change notification settings - Fork 18k
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
BUG (string dtype): comparison of string column to mixed object column fails #60228
Open
Tracked by
#54792
Comments
It seems we actually have a comment in the code about this issue in case of object dtype: pandas/pandas/core/arrays/arrow/array.py Lines 728 to 734 in 692ea6f
|
41 tasks
take |
TEARFEAR
added a commit
to TEARFEAR/pandas
that referenced
this issue
Nov 21, 2024
TEARFEAR
added a commit
to TEARFEAR/pandas
that referenced
this issue
Nov 21, 2024
TEARFEAR
added a commit
to TEARFEAR/pandas
that referenced
this issue
Nov 21, 2024
TEARFEAR
added a commit
to TEARFEAR/pandas
that referenced
this issue
Nov 22, 2024
TEARFEAR
added a commit
to TEARFEAR/pandas
that referenced
this issue
Nov 22, 2024
Open
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment you can freely compare with mixed object dtype column:
But with the string dtype enabled (using pyarrow), this now raises an error:
This happens because the ArrowEA tries to convert the
other
operand to Arrow as well, which fails for mixed types.In general, I think our rule is that
==
comparison never fails, but then just gives False for when values are not comparable.The text was updated successfully, but these errors were encountered: