CLN: _maybe_upcast_for_op doesn't need to check timedelta ndarray #40399
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
jorisvandenbossche
added
Clean
Numeric Operations
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.
The
elif isinstance(obj, np.ndarray) and obj.dtype.kind == "m":part is ever reached, because just before calling_maybe_upcast_for_op, we already did aensure_wrapped_if_datetimelikewhich basically does the same (codedov also confirms it's not covered). So therefore removing that check.In addition, moving the Datetime/TimedeltaArray inline within the
if/elifchecks, this gives a little bit less overhead for the non-datetimelike cases.