-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
BUG: series timedelta arithmetic is not being converted to ns with numpy 1.6 #4138
Conversation
Does the Travis fail mean that it will not be considered for merge? |
no that's unrelated just didn't get to it |
this was failing for numpy running on python 2.6 having to do with |
bug here is a bit more subtle because of numpy 1.6.x's different timedelta/datetime API. |
is Travis having numpy 1.6 with Python 2.6 only? Because I was using numpy 1.6 with Python 2.7 for, I believe, years! So that would be a much more realistic use case. |
short is answer is no, it's not :) |
ok, so that means the fail with the 2.6 env (or better to say locale?) can not have anything to do with numpy 1.6.1, because it works in 2.7, right? |
yes that's a different issue, as i pointed out above. before i was passing 2 args to timedelta64 which is invalid in numpy 1.6.x, now there's something else going on. |
@michaelaye no, in fact, i'm almost 100% sure it has something to do with 1.6.x. look at how the tests are run....
|
1.6.2 IS different (buggy basically).....will have to look at this |
oh, but the 3.2 env did work before, no? I thought I saw before that 2.6 env was the only one failing, so that must be your new test, I guess. (I am a noob about Travis, need to learn this ...) |
yep. before it was failing because you can't pass units to old timedelta (raising the standard |
just to make it even harder |
joy |
i think the type testing function is being too strict...checking it out now |
btw, we really should try and reduce the build time of the cython stuff by using fused types |
That's actually a question I had on my mind for months: I see that homebrew can build using all cores, but the pandas built ever only uses 1 core. How can one improve that? |
i think i fixed the arith issue, i wasn't converting to timedelta in the test...we'll see what happens |
@michaelaye not sure about that...i don't think you can parallelize that (easily) since |
but really i was referring to algos and things made by |
arg now it's failing because of something that looks minor. can't look at it right now ... |
if value.dtype != 'timedelta64[ns]': | ||
if np.__version__ < LooseVersion('1.7'): |
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.
maybe put this at the top of the file?
update: going to get to the bottom of why this works this weekend and if everything makes sense i'll write it up here and merge |
closing in favor of #4534 |
thanks |
closes #4135.