# 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 should appear first in case something else depends on pep8
hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0

coverage!=4.4,>=4.0 # Apache-2.0
ddt>=1.0.1 # MIT
mock>=2.0 # BSD
oslotest>=1.10.0 # Apache-2.0
pykmip>=0.5.0 # Apache 2.0 License
testrepository>=0.0.18 # Apache-2.0/BSD
testtools>=1.4.0 # MIT
fixtures>=3.0.0 # Apache-2.0/BSD
requests!=2.12.2,!=2.13.0,>=2.10.0 # Apache-2.0
WebTest>=2.0 # MIT
python-keystoneclient>=3.8.0 # Apache-2.0
tempest>=14.0.0 # Apache-2.0
python-subunit>=0.0.18 # Apache-2.0/BSD

# Bandit build requirements
bandit>=1.1.0 # Apache-2.0

# Documentation build requirements
sphinx!=1.6.1,>=1.5.1 # BSD
oslosphinx>=4.7.0 # Apache-2.0
os-api-ref>=1.0.0 # Apache-2.0
reno!=2.3.1,>=1.8.0 # Apache-2.0
openstackdocstheme>=1.5.0 # Apache-2.0