Skip to content

BUG: Scipy interpolate methods are not datetime64 aware #5975

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.

Sign up for GitHub

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

Jump to bottom
Closed
TomAugspurger opened this issue Jan 16, 2014 · 2 comments · Fixed by #5977 or #5998
Closed

BUG: Scipy interpolate methods are not datetime64 aware #5975

TomAugspurger opened this issue Jan 16, 2014 · 2 comments · Fixed by #5977 or #5998
Labels
Bug Dtype Conversions Unexpected or buggy dtype conversions Numeric Operations Arithmetic, Comparison, and Logical operations
Milestone
0.13.1

Comments

@TomAugspurger
Copy link
Contributor

From this SO question.

Is this something we should worry about here, or report upstream to scipy? The workaround I posted on SO is just to explicitly recast the index as an int64, interpolate on that, and then reset the original index. Any reason we shouldn't do this internally?
@jreback
Copy link
Contributor

jreback commented Jan 16, 2014

@TomAugspurger I think you may need to do a ``values.view('i8')` before passing if they are dtype.kind of 'M' or 'm'

@TomAugspurger TomAugspurger mentioned this issue Jan 16, 2014
Merged
@ghost
Copy link

ghost commented Jan 18, 2014

reopening for #5977 (comment)

@ghost ghost reopened this Jan 18, 2014
@TomAugspurger TomAugspurger mentioned this issue Jan 19, 2014
Merged
@ghost ghost closed this as completed in #5998 Jan 19, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Dtype Conversions Unexpected or buggy dtype conversions Numeric Operations Arithmetic, Comparison, and Logical operations
Projects
None yet
Milestone
0.13.1
2 participants
@jreback @TomAugspurger