# 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.2,<0.11  # Apache-2.0

coverage>=3.6  # Apache-2.0
python-subunit>=0.0.18  # Apache-2.0/BSD
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3  # BSD
oslosphinx>=2.5.0,!=3.4.0  # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
testrepository>=0.0.18  # Apache-2.0/BSD
testscenarios>=0.4  # Apache-2.0/BSD
testtools>=1.4.0  # MIT
trollius>=1.0  # Apache-2.0
eventlet!=0.18.3,>=0.18.2  # MIT
oslo.config!=3.18.0,>=3.14.0  # Apache-2.0    
oslo.log>=3.11.0  # Apache-2.0
oslo.concurrency>=3.8.0  # Apache-2.0
oslo.policy>=1.15.0  # Apache-2.0    
oslo.messaging>=5.2.0  # Apache-2.0 
oslo.db!=4.13.1,!=4.13.2,>=4.11.0  # Apache-2.0  
paramiko>=2.0.0  # LGPLv2.1+
pecan!=1.0.2,!=1.0.3,!=1.0.4,!=1.2,>=1.0.0  # BSD
PyMySQL>=0.7.6  # MIT License
SQLAlchemy!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8,>=1.0.10 # MIT
keystonemiddleware!=4.5.0,>=4.2.0 # Apache-2.0
autobahn>=0.10.1  # MIT License
WSME>=0.8  # MIT