BUG: Fix groupby().any() behavior for timedelta columns with all null valuesfix issue #59712 #59750
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.
This pull request addresses a bug in the
groupby().any()
method when applied to DataFrames withtimedelta
columns where all values are null (NaT
). Previously, the method incorrectly returnedTrue
for groups with all null values in thetimedelta
column.Changes Made:
_call_cython_op
method to correctly handletimedelta
columns when computing theany()
aggregation.groupby().any()
returnsFalse
for groups where alltimedelta
values are null.Issue Reference:
This fix ensures that the
groupby().any()
method behaves consistently fortimedelta
columns, aligning with the behavior observed for other data types.