TYP: Allow time manipulation functions to accept date
and timedelta
objects
#20763
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.
Backport of #20750
Closes #20746
The time manipulation functions (e.g.
busday_count
) are somewhat unique in that they unsafely cast many of their inputs todatetime64
ortimedelta64
arrays. This unsafe casting means that the conventionally usednpt.ArrayLike
alias is not comprehensive enough to capture all valid input types, most notably excludingdatetime.date
anddatetime.datetime
.This PR thus expands the relevant argument types with support for more
datetime
-based objects.