FIX BUG: Series constructor from dictionary drops key (index) levels when not all keys have same number of entries #60695 #60814
Conversation
This file contains 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
siber64
deleted the
BUG-#60695-Series-constructor-from-dictionary-drops-key-(index)-levels-when-not-all-keys-have-same-number-of-entries
branch
|
I saw unit test impacts in other areas where behaviour or MultiIndex changes. I have not addressed these as I had problems getting a clean unit test run. I'll need to pick through them carefully I think. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a simple fix, the keys were dropped from uneven tuples sue to zip behavior so I changed to zip_longest. I performance tested zip_longest and on equal length tuple pairs it actually outperforms zip - go figure.
Unit test is also added