-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
DEPR: Make FutureWarning into DeprecationWarning for groupby.apply #56952
DEPR: Make FutureWarning into DeprecationWarning for groupby.apply #56952
Conversation
We should get this in for 2.2 right? |
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.
Thanks!
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
thanks @rhshadrach. |
…onWarning for groupby.apply
#56964) * Backport PR #56952: DEPR: Make FutureWarning into DeprecationWarning for groupby.apply * Update test_groupby.py * fix finally? --------- Co-authored-by: Richard Shadrach <[email protected]>
…andas-dev#56952) * DEPR: Make FutureWarning into DeprecationWarning for groupby.apply * suppress extra warning when CoW warning mode --------- Co-authored-by: Joris Van den Bossche <[email protected]> Co-authored-by: Thomas Li <[email protected]>
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Ref: #54950 (comment)
cc @jorisvandenbossche @phofl
In the event we don't release a 2.3, I am okay waiting to enforce this deprecation until 4.0. The only downside I see of doing so is having users keep the shim
include_groups
for longer.