DEPR: apply/agg using agg/apply #42833
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g_no_apply_fallback � Conflicts: � pandas/core/apply.py � pandas/tests/groupby/test_groupby.py
…g_no_apply_fallback
jreback
added
Apply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A possible step toward #35725. Internally, agg may use apply and apply may use agg. Straightening these out so that agg always uses agg and apply always uses apply before changing the behavior of agg (without impacting apply).
This PR emits FutureWarning but with (a) no alternative to not get the warning and (b) no clear way for users to know what the future result may be (it may not even change). The only alternative ways forward I see here are
a. Change behavior with no warning
b. An option to switch between old/new implementation of apply/agg/transform as mentioned in #41112