BUG: fix subclass metadata preservation in groupby column selection #56761
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 small regression that was introduced with #51090 (in pandas 2.0): before that PR, the column subselection in the groupby code was done with a standard
__getitem__
call, while the PR introduced an optimized helper_getitem_nocopy
to avoid the copy that a standard__getitem__
does. However, that new helper forgot to add a__finalize__
call after_constructor
from a manager.The reason we noticed this in geopandas (geopandas/geopandas#3130) was to update our tests for the
apply
deprecation to include group columns (for which one alternative is to specifically select the non-group columns, but so that didn't work with recent pandas versions)