-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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 MultiIndex levels dropped #40701
BUG: RollingGroupby MultiIndex levels dropped #40701
Conversation
hmm should we target 1.2.4? e.g. how does this compare to that behavior (and how does that compare to 1.1.x)? |
It looks like you mentioned before this would be okay for 1.3 and we reverted this before for 1.2.x This gets us back to 1.1.3 behavior which was correct according to this bug report #38523 |
ok awesome |
doc/source/whatsnew/v1.3.0.rst
Outdated
@@ -693,6 +693,7 @@ Groupby/resample/rolling | |||
- Bug in :class:`core.window.ewm.ExponentialMovingWindow` when calling ``__getitem__`` would not retain ``com``, ``span``, ``alpha`` or ``halflife`` attributes (:issue:`40164`) | |||
- :class:`core.window.ewm.ExponentialMovingWindow` now raises a ``NotImplementedError`` when specifying ``times`` with ``adjust=False`` due to an incorrect calculation (:issue:`40098`) | |||
- Bug in :meth:`Series.asfreq` and :meth:`DataFrame.asfreq` dropping rows when the index is not sorted (:issue:`39805`) | |||
- Bug in :class:`core.window.rolling.RollingGroupby` where an level of a :class:`MultiIndex` would be dropped if it overlapped with a groupby label (:issue:`38787`, :issue:`38523`) |
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.
let's make this a full sub-section and mention this goes back to 1.1.x behavior
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.
Done
thanks @mroeschke |
Essentially #38737 but targeted for 1.3 as it appears that the current behavior is largely unexpected