Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Match Pandas logic for comparing two objects with nulls #7490
Match Pandas logic for comparing two objects with nulls #7490
Changes from 34 commits
9927d88
a707d78
1bdf1fc
d5d97be
0c65c90
138eaf8
290d443
8d8b7d2
0a591ec
38ef833
e49d6c5
4e87f75
8b4e3a0
cbe80dd
cc73371
0416671
3b87bfa
5b0230c
e652106
636c03a
ea66fe9
def3bd7
9f0e121
18c0eab
470975b
fbed297
7f7c345
c6150b7
bd23b19
d383ba0
952750c
6d7ffda
cf725ef
417d220
01876d2
63da3bf
981457d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
So, this PR broke tests for series and dataframe mixed arithmetic, because of course comparison ops are now producing different results. However upon investigating further, I realized that dataframe/series mixed arithmetic actually isn't working at all in some situations, and this test has a grievous error (of my own making of course) where it doesn't actually compare the results properly at the end of the test, hence the failure going unnoticed.
This led to PR #7491. However, these PRs are now mutually dependent in the sense that until this PR is merged, I can't actually fix that functionality unless I spend time making the results match the logic this PR is about to change.
It doesn't make sense to me to fix broken code to produce results that will shortly thereafter be changed, forcing me to redo the code/test again.
Let me know if this seems like a sensible way to proceed.
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.
cc @cwharris @shwina
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.
Synced offline and this plan seems like the least painful path forward (without having to merge 3 different PRs into a single one)