BUG: Fix assert_frame_equal dtype handling when check_dtype=False (#61473) #61525
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.
Fixes a bug in
assert_frame_equal
whereDataFrames
with logically equal values but different dtypes (nullable vs non-nullable) would raise errors even with check_dtype=False. Now, whencheck_dtype=False
, dtype mismatches won’t cause failures.closes BUG: assert_frame_equal(check_dtype=False) fails when comparing two DFs containing pd.NA that only differ in dtype (object vs Int32) #61473
Tests added and passing
Pre-commit checks passing
Added entry to v3.0.0.rst