-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Fix+test timedelta64(nat) ops #23425
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
Conversation
Hello @jbrockmendel! Thanks for submitting the PR.
|
Codecov Report
@@ Coverage Diff @@
## master #23425 +/- ##
==========================================
+ Coverage 92.25% 92.25% +<.01%
==========================================
Files 161 161
Lines 51186 51195 +9
==========================================
+ Hits 47222 47231 +9
Misses 3964 3964
Continue to review full report at Codecov.
|
result = obj - other | ||
tm.assert_equal(result, expected) | ||
with pytest.raises(TypeError): | ||
other - obj |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see a lot of error message changes. Are they tested anywhere with assert_raises_regex
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way these tests are parametrized, the messages are all over the place.
@@ -382,6 +383,12 @@ def _add_timedeltalike_scalar(self, other): | |||
Add a delta of a timedeltalike | |||
return the i8 result view | |||
""" | |||
if isna(other): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this pretty much what _nat_new did? I find this is repeating lots of code, why don't you make a method to create the null array instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_nat_new
also did casting+boxing that this doesn't. These two lines aren't repeated often enough to merit a method.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
pandas/core/arrays/period.py
Outdated
@@ -757,7 +759,12 @@ def _add_timedeltalike_scalar(self, other): | |||
assert isinstance(self.freq, Tick) # checked by calling function | |||
assert isinstance(other, (timedelta, np.timedelta64, Tick)) | |||
|
|||
delta = self._check_timedeltalike_freq_compat(other) | |||
if isna(other): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find the need to do this pretty odd, why would't the check routine handle this? I do not like special cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the first thing the check function does is call delta_to_nanoseconds
, which will raise if we pass np.timedelta64("NaT")
. Even if we change that method to avoid calling delta_to_nanoseconds
in that case, we'd need to handle a null return value after the check.
I do not like special cases
+1. As Joris mentioned in another thread, a lot of gymnastics seems to be driven by the fact that pd.NaT
does double-duty as both Not-A-Time and Not-A-Timedelta.
@@ -149,6 +149,8 @@ class PeriodArray(dtl.DatetimeLikeArrayMixin, ExtensionArray): | |||
period_array : Create a new PeriodArray | |||
pandas.PeriodIndex : Immutable Index for period data | |||
""" | |||
# array priority higher than numpy scalars | |||
__array_priority__ = 1000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a test that needs this? I agree should set it....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. IIRC it was timedelta64 - TimedeltaIndex
pandas/core/arrays/period.py
Outdated
if isna(other): | ||
# special handling for np.timedelta64("NaT"), avoid calling | ||
# _check_timedeltalike_freq_compat as that would raise TypeError | ||
delta = other |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you write this like
if notna(other):
# your current commnet
other = self.........
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure
@@ -1169,6 +1169,25 @@ def test_dti_isub_timedeltalike(self, tz_naive_fixture, two_hours): | |||
rng -= two_hours | |||
tm.assert_index_equal(rng, expected) | |||
|
|||
def test_dt64arr_add_sub_td64_nat(self, box, tz_naive_fixture): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you parameterize other with pd.NaT as well here (I bet we already have a test for that, can you consolidate)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really; pd.NaT behavior is pretty starkly different from the behavior we’re testing here.
That said, there are several rounds of de duplication and parameterization coming up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how is it different at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because this is a timedelta64 and pd.NaT is in most cases datetime-like. The "most cases" part makes it especially hairy.
@@ -785,6 +785,24 @@ def test_pi_add_sub_timedeltalike_freq_mismatch_monthly(self, | |||
with tm.assert_raises_regex(period.IncompatibleFrequency, msg): | |||
rng -= other | |||
|
|||
def test_parr_add_sub_td64_nat(self, box): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
@@ -735,6 +735,24 @@ def test_td64arr_add_sub_tdi(self, box_df_broadcast_failure, names): | |||
else: | |||
assert result.dtypes[0] == 'timedelta64[ns]' | |||
|
|||
def test_td64arr_add_sub_td64_nat(self, box): | |||
# GH#23320 special handling for timedelta64("NaT") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
lgtm. can you rebase. ping on green. |
Fixes issues mentioned as follow-ups to #23320
git diff upstream/master -u -- "*.py" | flake8 --diff