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.
Preserve EA dtype in DataFrame.stack #23285
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
Preserve EA dtype in DataFrame.stack #23285
Changes from all commits
381b073
428f230
0d39be0
fc37932
7bb5a5e
7e9224a
d6661cb
3d41f5b
9f91df0
144d117
98f75c9
88f7f3e
2b858b8
88f08c7
d305c86
f6aeafa
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is kinda strange. For
DataFrame[ndarray[object]].stack()
of all periods, we actually inferperiod
-dtype. Do we want that, or should we explicitly passdtype=object
when creating the new series / frame to ensure that we don't infer the "correct" dtype?(that's on master)