-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Support numpy 1.8 #5412
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
Comments
@cpcloud were u going to setup a wheel for this one? (1.8)? |
https://travis-ci.org/jreback/pandas/builds/13386292 works....takes 8 minutes longer (total)...w/o wheels |
What is a wheel? |
Also how closely does the pydata team collaborate with the numpy team on matter such as datetime support? |
@cpcloud basically made binary installables for long-to-compile (e.g. numpy/scipy) that work on the travis boxes. so you just download the image and done, no need to get a version and compile, much faster. 2nd question - no collaboration, just if we find bugs they are pushed upstream (though mainly they are worked around , e.g. 1.6.2 basically broken). |
And numpy tests pandas around releases. Is there anything we really wish |
datetime support is fine (well maybe if they add proper tz support but who knows) |
Numpy 1.8 was released recently - https://github.com/numpy/numpy/blob/master/doc/release/1.8.0-notes.rst
We should probably support it and add/change a Travis build for it. Additionally, might be interesting to benchmark numpy's nanmean, nanvar and nanstd against pandas versions...
numpy also notes that they are planning to make more datetime changes in 1.9 - whee!
The text was updated successfully, but these errors were encountered: