Skip to content

BUG: assert_index_equal defaults to check_exact_index=False on integers #57386

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

Closed
rhshadrach opened this issue Feb 12, 2024 · 2 comments · Fixed by #58189
Closed

BUG: assert_index_equal defaults to check_exact_index=False on integers #57386

rhshadrach opened this issue Feb 12, 2024 · 2 comments · Fixed by #58189
Labels
API - Consistency Internal Consistency of API/Behavior Bug Testing pandas testing functions or related to the test suite
Milestone

Comments

@rhshadrach
Copy link
Member

Ref: #57341 (comment)

@rhshadrach rhshadrach added Bug Testing pandas testing functions or related to the test suite API - Consistency Internal Consistency of API/Behavior labels Feb 12, 2024
@rhshadrach rhshadrach added this to the 3.0 milestone Feb 12, 2024
@Aloqeely
Copy link
Member

Aloqeely commented Apr 7, 2024

Sorry but I don't understand what the bug is from the title, looking at assert_index_equal's parameters I can see that check_exact always defaults to True
Looking at the comment, maybe you meant that check_exact_index in assert_series_equal defaults to False for integers?

@rhshadrach rhshadrach changed the title BUG: assert_index_equal defaults to check_exact=False on integers BUG: assert_index_equal defaults to check_exact_index=False on integers Apr 8, 2024
@rhshadrach
Copy link
Member Author

maybe you meant that check_exact_index in assert_series_equal defaults to False for integers?

Yes - thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API - Consistency Internal Consistency of API/Behavior Bug Testing pandas testing functions or related to the test suite
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants