Skip to content

BUG: Fixed timedelta numeric operations #18892

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

Closed
wants to merge 1 commit into from

Conversation

TomAugspurger
Copy link
Contributor

Closes #18880

@TomAugspurger TomAugspurger added Numeric Operations Arithmetic, Comparison, and Logical operations Timedelta Timedelta data type labels Dec 21, 2017
@TomAugspurger TomAugspurger added this to the 0.22.0 milestone Dec 21, 2017
@@ -888,6 +888,19 @@ def test_nanstd_roundoff(self):
result = data.std(ddof=ddof)
assert result == 0.0

def test_nanvar_timedelta(self):
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this should be done up in TestnanopsDataFrame but I cannot figure out what's going on in those tests. test_nanstd and test_nanvar both have allow_tdelta=True, but were not catching the bug in #18880

@TomAugspurger
Copy link
Contributor Author

Doesn't seem like this is going to work without causing overflows everywhere...

@@ -338,7 +338,8 @@ Reshaping
Numeric
^^^^^^^

-
- Fixed ``std`` and ``var`` computations for timedelta arrays not returning results in timedelta units (:issue:`18880`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a fix for 0.22? or for 0.23? (IOW do you need to have this for nansum)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was was specific to nanstd, so I think I can work around it. The skipna stuff affected all the ops I think. I'll see how hard that is to work around.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah rather leave this alone for now (IOW do it in 0.23).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rebase on master. can you move to 0.23 (docs were renamed), prob easiest to just check this file from master and past in new one

@jreback jreback modified the milestones: 0.22.0, 0.23.0 Dec 21, 2017
@@ -338,7 +338,8 @@ Reshaping
Numeric
^^^^^^^

-
- Fixed ``std`` and ``var`` computations for timedelta arrays not returning results in timedelta units (:issue:`18880`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rebase on master. can you move to 0.23 (docs were renamed), prob easiest to just check this file from master and past in new one

@jreback
Copy link
Contributor

jreback commented Feb 1, 2018

can you move the release note and update

@jreback
Copy link
Contributor

jreback commented Mar 16, 2018

can you rebase

@jreback jreback removed this from the 0.23.0 milestone Apr 1, 2018
@jreback
Copy link
Contributor

jreback commented Apr 1, 2018

needs a rebase

@TomAugspurger TomAugspurger deleted the var-timedelta branch May 2, 2018 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Numeric Operations Arithmetic, Comparison, and Logical operations Timedelta Timedelta data type
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants