Keep the MultiIndex of the df even if empty #188
Merged
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.
I just faced this:
copy.index
was an emptypd.MultiIndex
with specified columns['FrameId', 'Event']
, as it was supposed to be.Index
(notMultiIndex
) without any specified columns.r
further on: its index also became justIndex
, though, with a tuple in each entry. This screwed upr.index.get_level_values(0).max() + 1
because you cannot add1
to a tuple.The proposed change should prevent this from happening while maintaining the intended behavior.
I am using pandas==2.1.2 and Python 3.10