BUG: Updated _pprint_seq to use enumerate instead of next #57295
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.
This PR closes an edge-case bug that has been around for almost 7 years.
To print a DataFrame, the function
_pprint_seq()
constructs a string representation of an iterable object (calledseq
) by creating an iterator over it, and truncating it iflen(seq) > max_seq_items
.However, a pandas
DataFrame
is an example of an object wherelen(seq)
is not a valid way of checking the length of the iterator. Specifically,len(df)
returns the number of rows, whileiter(df)
iterates over the columns. When trying to print a DataFrame with more rows than columns, this raises aStopIterator
exception.This PR fixes this bug by explicitly iterating over the object, rather than assuming that
len(seq)
is equal to the number of items in the object. The new testtest_nested_dataframe()
raises an exception onmain
, but passes on this branch.doc/source/whatsnew/v3.0.0.rst
.