# 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.11,>=0.10.0
coverage>=3.6 # Apache-2.0
fixtures<2.0,>=1.3.1 # Apache-2.0/BSD
mock>=1.2 # BSD
mox3>=0.7.0 # Apache-2.0
psycopg2>=2.5 # LGPL/ZPL
PyMySQL>=0.6.2 # MIT License
python-barbicanclient>=4.0.0 # Apache-2.0
python-ironicclient>=1.1.0 # Apache-2.0
python-subunit>=0.0.18 # Apache-2.0/BSD
requests-mock>=0.7.0 # Apache-2.0
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD
os-api-ref>=0.1.0 # Apache-2.0
oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
os-testr>=0.4.1 # Apache-2.0
testrepository>=0.0.18 # Apache-2.0/BSD
testresources>=0.2.4 # Apache-2.0/BSD
testtools>=1.4.0 # MIT
tempest-lib>=0.14.0 # Apache-2.0
bandit>=1.0.1 # Apache-2.0
openstackdocstheme>=1.0.3 # Apache-2.0

# vmwareapi driver specific dependencies
oslo.vmware>=1.16.0 # Apache-2.0

# releasenotes
reno>=1.6.2 # Apache2