-
Notifications
You must be signed in to change notification settings - Fork 129
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
pandas version #144
Comments
pandas release notes indicate 0.18 had breaking changes, and I did not audit 0.18's changes, or the breaking changes of even newer releases, against augur's usage of pandas. This may be me being over-conservative. It would be less conservative, but still reasonable, to set minimums that are known good and accept the possibility of breakage from new versions we haven't tried. |
on various systems I had 0.19, 0.20, 0.21 installed. haven't run into any problems. I think minimum req are fine. If we are incompatible with latest numpy, scipy, pandas, we better find out about it sooner rather than later. |
Nod. My previous flurry of changes to deps were all based around the previous |
I would say to upgrade pandas version across the board. Keep it the same for |
I removed the upper bound in augur. we only use it to read csv.... |
why do we restrict pandas version to <0.18 (9d1b078). 0.17 is >2y old and the current stable version is 0.23. any known incompatibilities @trvrb @tsibley
The text was updated successfully, but these errors were encountered: