# 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

-e git+https://git.openstack.org/openstack/neutron.git@stable/pike#egg=neutron
-e git+https://git.openstack.org/openstack/tap-as-a-service.git@stable/pike#egg=tap-as-a-service
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.privsep>=1.9.0  # Apache-2.0
pyroute2==0.4.17  # Apache-2.0 (+ dual licensed GPL2)
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
tempest>=17.1.0  # Apache-2.0
babel!=2.4.0,>=2.3.4
os-vif>=1.1.0 # Apache-2.0
stestr>=1.0.0 # Apache-2.0
