# 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.10.0,<0.11

-e git+https://git.openstack.org/openstack/neutron.git@liberty-eol#egg=neutron
cliff>=1.7.0  # Apache-2.0
coverage>=3.6
discover
mock>=1.0
fixtures>=1.3.1
python-subunit>=0.0.18
requests-mock>=0.5.1  # Apache-2.0
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
oslosphinx>=2.2.0  # Apache-2.0
oslo.db!=4.13.1,!=4.13.2,>=4.10.0,<4.19.0 # added until upstream patches
testrepository>=0.0.18
testresources>=0.2.4 # Apache-2.0/BSD
testtools>=0.9.36,!=1.2.0
testscenarios>=0.4
WebTest>=2.0
oslotest>=1.2.0  # Apache-2.0
oslo.log>=1.14.0,<3.21.0 # Apache-2.0
tempest-lib>=0.2.0
kombu>=3.0.25,<4.0.0 # BSD
