Update test-requirements.txt

The testing requirements should not cause extra packaging
work for deployers (since these aren't required to deploy).
This patch brings it in line with the latest global requirements,
except for python-swiftclient itself (which I kept with no version
specifier). By being in line with global requirements, this is a
more accurate list with respect to how things are actually tested
in the gate.

Change-Id: Iddc92d9bb135144d38c3e5aec2e95df5787e9b5b
This commit is contained in:
John Dickinson 2016-09-03 10:18:32 -07:00
parent 7dcfe5a7ec
commit 396baf4139

View File

@ -3,19 +3,19 @@
# process, which may cause wedges in the gate later. # process, which may cause wedges in the gate later.
# Hacking already pins down pep8, pyflakes and flake8 # Hacking already pins down pep8, pyflakes and flake8
hacking>=0.10.0,<0.11 hacking>=0.11.0,<0.12 # Apache-2.0
coverage coverage>=3.6 # Apache-2.0
nose nose # LGPL
nosexcover nosexcover # BSD
nosehtmloutput nosehtmloutput>=0.0.3 # Apache-2.0
openstackdocstheme>=1.0.3 # Apache-2.0 openstackdocstheme>=1.5.0 # Apache-2.0
oslosphinx oslosphinx>=4.7.0 # Apache-2.0
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3 # BSD sphinx!=1.3b1,<1.4,>=1.2.1 # BSD
os-api-ref>=0.1.0 # Apache-2.0 os-api-ref>=1.0.0 # Apache-2.0
os-testr>=0.4.1 os-testr>=0.8.0 # Apache-2.0
mock>=1.0 mock>=2.0 # BSD
python-swiftclient python-swiftclient
python-keystoneclient>=1.3.0 python-keystoneclient!=2.1.0,>=2.0.0 # Apache-2.0
# Security checks # Security checks
bandit>=1.1.0 # Apache-2.0 bandit>=1.1.0 # Apache-2.0