-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
overflow checks for Series operations #18802
Comments
@jbrockmendel : That's an interesting suggestion. Since this is pretty invasive, I'm not sure if we would actually tackle this for some time. Would be good for |
@jbrockmendel : Oh, don't close this! 😄 Keep it open. This is a very valid issue to raise. It just may not be addressed for some time give the invasiveness. |
The idea was to roll it into #18824. I’m happy either way. |
Ah, gotcha. Just for future reference, add a comment that you're doing this so that we're all on the same page. 😄 |
Spending some time on #12534 the only fixes I'm seeing are pretty invasive. We need to use
checked_add_with_arr
to correctly catch overflows, and for that we needisna(...)
masks. But the wrapping/redirection that goes on withinops._arith_method_SERIES
make that problematic. In particular the scope in which the masks are defined (for datetime/timedelta dtypes) is different from the scope in which we need to do the overflow checking. Passing those masks back and forth across scopes gets ugly in a hurry.I'd rather just define
__add__
,__sub__
,__radd__
,__rsub__
methods specific to datetimelike-dtypes and have Series dispatch to those when appropriate. Any thoughts?The text was updated successfully, but these errors were encountered: