-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: rolling.groupby with on and __getitem__ doesn't mutate underlying object #43374
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: rolling.groupby with on and __getitem__ doesn't mutate underlying object #43374
Conversation
mroeschke
commented
Sep 3, 2021
- closes BUG: Groupby rolling count gives inconsistent outputs with missing index #43355
- tests added / passed
- Ensure all linting tests pass, see here for how to run them
- whatsnew entry
doc/source/whatsnew/v1.4.0.rst
Outdated
@@ -398,6 +398,7 @@ Groupby/resample/rolling | |||
- Bug in :meth:`pandas.DataFrame.rolling` operation along rows (``axis=1``) incorrectly omits columns containing ``float16`` and ``float32`` (:issue:`41779`) | |||
- Bug in :meth:`Resampler.aggregate` did not allow the use of Named Aggregation (:issue:`32803`) | |||
- Bug in :meth:`Series.rolling` when the :class:`Series` ``dtype`` was ``Int64`` (:issue:`43016`) | |||
- Bug in :meth:`DataFrame.groupby.rolling` when specifying ``on`` and calling ``__getitem__`` would return subsequent incorrect results (:issue:`43355`) |
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.
"return subsequent" -> "subsequently return"?
Thanks @mroeschke This does not close the issue? (as indicated in the OP) There are still the issues of the inconsistent indexes between |
Thanks @mroeschke
there was a typo here. the index didn't change from 1.2.5, the result columns did. There was a change in index from 1.1.5. I've commented on the issue. #43405 (comment) |
…ng_on_getitem_mutate
…ng_on_getitem_mutate
thanks @mroeschke |