# 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!=0.13.0,<0.14,>=0.12.0 # Apache-2.0

astroid<1.4.0 # LGPLv2.1 # breaks pylint 1.4.4
coverage!=4.4,>=4.0 # Apache-2.0
fixtures>=3.0.0 # Apache-2.0/BSD
flake8-import-order==0.12 # LGPLv3
mock>=2.0 # BSD
pylint==1.4.5 # GPLv2
python-subunit>=0.0.18 # Apache-2.0/BSD
requests-mock>=1.1 # Apache-2.0
sphinx>=1.6.2 # BSD
openstackdocstheme>=1.16.0 # Apache-2.0
testrepository>=0.0.18 # Apache-2.0/BSD
tempest>=16.1.0 # Apache-2.0
testtools>=1.4.0 # MIT
testresources>=0.2.4 # Apache-2.0/BSD
testscenarios>=0.4 # Apache-2.0/BSD
WebOb>=1.7.1 # MIT
WebTest>=2.0 # MIT
oslotest>=1.10.0 # Apache-2.0
reno!=2.3.1,>=1.8.0 # Apache-2.0
os-testr>=0.8.0 # Apache-2.0
