Use pur to upgrade python packages

[humitos]

$ pur --skip django-tastypie,django,docker-py,elasticsearch,pyelasticsearch,commonmark,stripe,djangorestframework,mkdocs,django-allauth
Updated pip: 9.0.3 -> 10.0.0
Updated virtualenv: 15.1.0 -> 15.2.0
Updated Sphinx: 1.7.0 -> 1.7.2
Updated sphinx-rtd-theme: 0.2.5b1 -> 0.3.0
New version for readthedocs-build found (2.0.9), but current spec prohibits updating: readthedocs-build<2.1
Updated django-haystack: 2.7.0 -> 2.8.1
Updated django-extensions: 2.0.0 -> 2.0.6
Updated django-vanilla-views: 1.0.4 -> 1.0.5
Updated lxml: 4.1.1 -> 4.2.1
Updated httplib2: 0.10.3 -> 0.11.3
Updated GitPython: 2.1.8 -> 2.1.9
Updated pytz: 2018.3 -> 2018.4
Updated docker: 3.1.3 -> 3.2.1
Updated sphinxcontrib-httpdomain: 1.6.0 -> 1.6.1
Updated packaging: 16.8 -> 17.1
All requirements up-to-date.

[stsewd]

I think we should wait until readthedocs/sphinx_rtd_theme#610 is solved, right?

[davidfischer]

Good call. Let's hold off on this one for now. I'm going to try to get the issues around this resolved.

[humitos]

I will stick in 0.2.5b1 until that issue is solved.

[stsewd]

I think this is only used on the API v1, is still worth updating? 🤔

[humitos]

Isn't this used for elasticsearch?

[ericholscher]

No. It's only for v1 API which we should deprecate.

[ericholscher]

Looks good, though I do worry about breaking stuff that isn't well tested (eg. Docker). It's good to keep these up to date though, so I'm +1 on merging it and then doing dev with it for a while before deploying.

[humitos]

I did some tests locally running different builds and it worked. The good side is that we have a newer version of docker daemon in our servers so it's more likely to be compatible without changes.