0d37492c65
* Drop osc from test-requirements (and lower-constraints) I'm not clear on where/how we use it; I think it was a hold-over from swift3? * Pin python-keystoneclient in our py2-constraints Something sees to have changed with the pip resolver that means it keeps trying to install a newer, py3-only version for our py2 jobs. Change-Id: Ie37ac077517e1ece5fa6bf163d1ab5e316ced509
26 lines
776 B
Plaintext
26 lines
776 B
Plaintext
# 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.
|
|
|
|
# Hacking already pins down pep8, pyflakes and flake8
|
|
hacking>=2.0,<2.1.0 # Apache-2.0
|
|
coverage>=3.6 # Apache-2.0
|
|
nose>=1.3.7 # LGPL
|
|
nosexcover>=1.0.10 # BSD
|
|
nosehtmloutput>=0.0.3 # Apache-2.0
|
|
os-testr>=0.8.0 # Apache-2.0
|
|
mock>=2.0 # BSD
|
|
python-swiftclient>=3.2.0
|
|
python-keystoneclient!=2.1.0,>=2.0.0 # Apache-2.0
|
|
boto>=2.32.1
|
|
boto3>=1.9
|
|
botocore>=1.12
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
keystonemiddleware>=4.17.0 # Apache-2.0
|
|
|
|
# Security checks
|
|
bandit>=1.1.0 # Apache-2.0
|
|
|
|
docutils>=0.11 # OSI-Approved Open Source, Public Domain
|