-
Notifications
You must be signed in to change notification settings - Fork 57
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
add gokart.testing.assert_frame_equal #256
add gokart.testing.assert_frame_equal #256
Conversation
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.
The most exciting PR in recent times.
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.
Need a explanation of difference from pd.testing.assert_frame_equal
, plz
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.
Thanks! LGTM
@mski-iksm thx I've understand functionalities! IMO, how about more descriptive name indicating difference (e.g. assert_frame_contents_equal, assert_frame_equal_ignoring_index) |
I agree with your idea. I've changed the method name assert_frame_equal -> assert_frame_contents_equal . Please review. |
@mski-iksm 🆒 LGTM! |
@mski-iksm Thx for cool function :) Merged! |
I've added a new feature
gokart.testing.assert_frame_equal()
for comparing pd.DataFrame.As mentioned in the issue, this is useful when index/columns orders are different.
Related issue: #243 raised by @vaaaaanquish
Please review!