Fix DataFrame.info() tests for pandas 2.0#9909
Merged
jrbourbeau merged 1 commit intodask:mainfrom Feb 2, 2023
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
dask/dataframe/tests/test_dataframe.py::test_infoanddask/dataframe/tests/test_dataframe.py::test_categorize_infoare failing in ourupstreambuild due to the use of hard-coded expected output that is slightly different when usingpandas2.0. This PR generalizes the hard-coded value a bit to make things work.Note that I think we could probably re-work our
info-related tests to not use hard-coded values at all, but that will take more time, so I'm going with the simple fix here.cc @j-bennet