# 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. # Temporarily add Babel reference to avoid problem # in keystone-coverage-db CI job Babel>=2.3.4 # BSD pbr>=1.6 # Apache-2.0 WebOb>=1.2.3 # MIT PasteDeploy>=1.5.0 # MIT Paste # MIT Routes!=2.0,!=2.1,!=2.3.0,>=1.12.3;python_version=='2.7' # MIT Routes!=2.0,!=2.3.0,>=1.12.3;python_version!='2.7' # MIT cryptography!=1.3.0,>=1.0 # BSD/Apache-2.0 six>=1.9.0 # MIT SQLAlchemy<1.1.0,>=1.0.10 # MIT sqlalchemy-migrate>=0.9.6 # Apache-2.0 stevedore>=1.16.0 # Apache-2.0 passlib>=1.6 # BSD python-keystoneclient!=1.8.0,!=2.1.0,>=1.7.0 # Apache-2.0 keystonemiddleware!=4.1.0,!=4.5.0,>=4.0.0 # Apache-2.0 oslo.cache>=1.5.0 # Apache-2.0 oslo.concurrency>=3.8.0 # Apache-2.0 oslo.config>=3.12.0 # Apache-2.0 oslo.context!=2.6.0,>=2.4.0 # Apache-2.0 oslo.messaging>=5.2.0 # Apache-2.0 oslo.db>=4.1.0 # Apache-2.0 oslo.i18n>=2.1.0 # Apache-2.0 oslo.log>=1.14.0 # Apache-2.0 oslo.middleware>=3.0.0 # Apache-2.0 oslo.policy>=1.9.0 # Apache-2.0 oslo.serialization>=1.10.0 # Apache-2.0 oslo.utils>=3.16.0 # Apache-2.0 oauthlib>=0.6 # BSD pysaml2<4.0.3,>=2.4.0 # Apache-2.0 dogpile.cache>=0.6.1 # BSD jsonschema!=2.5.0,<3.0.0,>=2.0.0 # MIT pycadf!=2.0.0,>=1.1.0 # Apache-2.0 msgpack-python>=0.4.0 # Apache-2.0 osprofiler>=1.3.0 # Apache-2.0