-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: RollingGroupby no longer keeps the groupby column in the result #40341
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
BUG: RollingGroupby no longer keeps the groupby column in the result #40341
Conversation
cc @pandas-dev/pandas-core, @pandas-dev/pandas-triage if any comments (this was a discussion item on the call i think month before last) |
@@ -558,6 +558,10 @@ def __init__( | |||
if _grouper is None: | |||
raise ValueError("Must pass a Grouper object.") | |||
self._grouper = _grouper | |||
# GH 32262: It's convention to keep the grouping column in |
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.
is the difference in conventions just a historical thing? might we want to make these match eventually?
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.
Seems to be historical #32332 (review)
Would be great to have groupby apply match but might take come convincing
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.
LGTM
thanks @mroeschke |
Borrowed some work from #32332