-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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: Fix assert_equal when check_exact=True for non-numeric dtypes #3… #35522
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.
looks good @ivirshup; can you add a note in the 1.1.1 docs (regression section). ping on green.
f28307e
to
95b766c
Compare
@jreback, added the release note, and it's kinda green. It looks like one of the jobs timed out though. |
restarted |
also pls merge master |
Made those changes. How is it now? |
thanks! |
@meeseeksdev backport 1.1.x |
…True for non-numeric dtypes pandas-dev#3…
…on-numeric dtypes #3… (#35652) Co-authored-by: Isaac Virshup <[email protected]>
assert_series_equal(..., check_exact=True)
no longer raises an error when series has a non-numeric dtype. This fixes a bug/ regression introduced in1.1.0
.black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff
I've added a very simple test, but could add more. For instance, there could be a check on
assert_frame_equal
, but I'm not sure what the desired strategy is for that.I've left off the
whatsnew
entry for now since I figure that's the most likely to generate conflicts while this gets reviewed.