pandas version

[nextstrain]

pandas version

[tsibley]

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.

[rneher]

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.

[tsibley]

Nod. My previous flurry of changes to deps were all based around the previous requirements.txt files that were kept manually pinned to exact versions. This change will be a further departure from those, but I think that's ok. @trvrb?

[trvrb]

I would say to upgrade pandas version across the board. Keep it the same for fauna/requirements.txt, augur/requirement.txt and augur/setup.py. And quickly confirm nothing breaking with upgrades. Would be nice to keep dependency versions consistent across components. Certainly makes pip installs easier.

[rneher]

I removed the upper bound in augur. we only use it to read csv....