# 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 # BSD python-subunit>=0.0.18 # Apache-2.0/BSD sphinx!=1.6.1,>=1.5.1 # BSD psycopg2>=2.5 # LGPL/ZPL PyMySQL>=0.7.6 # MIT License oslosphinx>=4.7.0 # Apache-2.0 oslotest>=1.10.0 # Apache-2.0 oslo.privsep>=1.9.0 # Apache-2.0 pyroute2>=0.4.12 # Apache-2.0 (+ dual licensed GPL2) testrepository>=0.0.18 # Apache-2.0/BSD testresources>=0.2.4 # Apache-2.0/BSD testtools>=1.4.0 # MIT testscenarios>=0.4 # Apache-2.0/BSD WebTest>=2.0 # MIT # This is needed for subunit-trace reno>=1.8.0 # Apache-2.0 bandit>=1.1.0 # Apache-2.0 tempest>=14.0.0 # Apache-2.0 pylint==1.4.5 # GPLv2 python-openstackclient>=3.3.0 # Apache-2.0 requests-mock>=1.1 # Apache-2.0 pyshark>=0.3.7.2 # pyshark