-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Certain comparison operations misbehaving for period dtype #28980
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
Labels
Milestone
Comments
4 tasks
xref #24576 suggesting that _unbox_scalar can be used to unify some of the logic in these comparison ops |
Would it make sense to have the parsing be optional since some comparisons may not require it? The comparison itself could then handle any failed casting. |
Looks to work on master now. Could use a test
|
OlivierLuG
pushed a commit
to OlivierLuG/pandas
that referenced
this issue
May 27, 2020
OlivierLuG
pushed a commit
to OlivierLuG/pandas
that referenced
this issue
May 28, 2020
jreback
pushed a commit
that referenced
this issue
May 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This is closely related to #28930.
yields
but the output should be
Series([False, False])
. The other comparison operators<
,<=
,>
, and>=
yield the same error, which also seems incorrect (the error message should probably be different, and the error should be aTypeError
rather than aValueError
). This is happening on 0.25.1 and master.The text was updated successfully, but these errors were encountered: