summaryrefslogtreecommitdiff
path: root/requirements.txt
diff options
context:
space:
mode:
authorTim Burke <tim.burke@gmail.com>2018-05-16 17:33:40 +0000
committerTim Burke <tim.burke@gmail.com>2018-07-11 13:09:00 -0700
commitda362a653e9c70cb6ae17a7c3764887b4fd3fcf2 (patch)
treed705e880aff1078d8b1cb7228e629f9003bf655c /requirements.txt
parentc2c5af603f8ae25be052a20b02dc109b0f8f014a (diff)
downloadpython-swiftclient-da362a653e9c70cb6ae17a7c3764887b4fd3fcf2.tar.gz
Back out some version bumps
I'm giving up on trying to back out all of the test-requirements up-revs, but let's try to stay compatibile with old requests/six. As part of that, only disable some requests warnings on new-enough requests. Note that we should now be compatible with distro packages back to Ubuntu 16.04 and CentOS 6. Our six is still too new for Trusty, but hey, there's less than a year left on that anyway, right? Change-Id: Iccb23638393616f9ec3da660dd5e39ea4ea94220 Related-Change: I2a8f465c8b08370517cbec857933b08fca94ca38
Diffstat (limited to 'requirements.txt')
-rw-r--r--requirements.txt7
1 files changed, 2 insertions, 5 deletions
diff --git a/requirements.txt b/requirements.txt
index 6b52791..1c2ce33 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,6 +1,3 @@
-# The order of packages is significant, because pip processes them in the order
-# of appearance. Changing the order has an impact on the overall integration
-# process, which may cause wedges in the gate later.
futures>=3.0.0;python_version=='2.7' or python_version=='2.6' # BSD
-requests>=2.14.2 # Apache-2.0
-six>=1.10.0 # MIT
+requests>=1.1.0
+six>=1.9.0