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.
BUG: Set check_exact to true if dtype is int #55934
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: Set check_exact to true if dtype is int #55934
Changes from 8 commits
4eabcd6
bce3087
8fd5e61
c3ecb84
6d74ec3
8f608a0
c46b2d6
a4eabea
00b7c91
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.
This is a different issue than reported in #56131 (there is also no
check_dtype=False
here)This doesn't involve different data types (it's all numpy dtypes), and the two objects created here seemingly are the same:
But apparently we have a bug in the Series constructor that preserves the masked array as underlying value if it has no masked elements:
That seems like a separate, actual bug we should solve, regardless of the behaviour of
check_dtype
in assert_series_equal (although being more strict here actually uncovered this bug ..)