6828a01eac
The requirements check doesn't like it when upper-constraints isn't the authoritative upper bound for a dependency. upper-constraints already caps this library at 2.6.0. Change-Id: I6033066b5e2fafb3104f7c9e1642c9b51ca923d0
45 lines
1.4 KiB
Plaintext
45 lines
1.4 KiB
Plaintext
# 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.4.0,>=2.3.4 # BSD
|
|
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
WebOb>=1.7.1 # MIT
|
|
Flask!=0.11,>=1.0.2 # BSD
|
|
Flask-RESTful>=0.3.5 # BSD
|
|
cryptography>=2.1 # BSD/Apache-2.0
|
|
six>=1.10.0 # MIT
|
|
SQLAlchemy>=1.1.0 # MIT
|
|
sqlalchemy-migrate>=0.11.0 # Apache-2.0
|
|
stevedore>=1.20.0 # Apache-2.0
|
|
passlib>=1.7.0 # BSD
|
|
python-keystoneclient>=3.8.0 # Apache-2.0
|
|
keystonemiddleware>=5.1.0 # Apache-2.0
|
|
bcrypt>=3.1.3 # Apache-2.0
|
|
scrypt>=0.8.0 # BSD
|
|
oslo.cache>=1.26.0 # Apache-2.0
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.context>=2.22.0 # Apache-2.0
|
|
oslo.messaging>=5.29.0 # Apache-2.0
|
|
oslo.db>=4.27.0 # Apache-2.0
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
oslo.log>=3.38.0 # Apache-2.0
|
|
oslo.middleware>=3.31.0 # Apache-2.0
|
|
oslo.policy>=1.43.1 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.upgradecheck>=0.1.0 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
oauthlib>=0.6.2 # BSD
|
|
pysaml2>=4.5.0
|
|
PyJWT>=1.6.1 # MIT
|
|
dogpile.cache>=0.6.2 # BSD
|
|
jsonschema>=2.6.0 # MIT
|
|
pycadf!=2.0.0,>=1.1.0 # Apache-2.0
|
|
msgpack>=0.5.0 # Apache-2.0
|
|
osprofiler>=1.4.0 # Apache-2.0
|
|
pytz>=2013.6 # MIT
|