# 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

coverage!=4.4,>=4.0 # Apache-2.0
fixtures>=3.0.0 # Apache-2.0/BSD
mock>=2.0.0 # BSD
python-subunit>=0.0.18 # Apache-2.0/BSD
sphinx>=1.6.2 # BSD
ddt>=1.0.1 # MIT
oslosphinx>=4.7.0 # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
testrepository>=0.0.18 # Apache-2.0/BSD
testresources>=0.2.4 # Apache-2.0/BSD
testscenarios>=0.4 # Apache-2.0/BSD
testtools>=1.4.0 # MIT
sphinxcontrib-pecanwsme>=0.8.0 # Apache-2.0
sphinxcontrib-seqdiag # BSD
reno>=2.5.0 # Apache-2.0
os-api-ref>=1.0.0 # Apache-2.0
tempest>=16.1.0 # Apache-2.0

eventlet>=0.17.4
keystonemiddleware==4.4.1
oslo_versionedobjects>=1.8.0
pecan>=1.0.2
oslo.db>=4.7.1
wsme>=0.8.0
oslo.policy>=1.6.0
oslo.utils>=3.8.0
jsonpatch>=1.14