bf863c5e3a
Previous versions of jsonschema (<3.2.0) doesn't support python 3.8 [1]. Python 3.8 is part of the victoria supported runtimes [2] so we now force to use jsonschema version 3.2.0 to avoid issues, remove ambiguity and ensure that everything works with python 3 in general. [1] https://github.com/Julian/jsonschema/pull/627 [2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria Change-Id: Id7e0f5b9c2c54ec0d5f1f7b0cd8199bc60718971
35 lines
1.1 KiB
Plaintext
35 lines
1.1 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.
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
|
|
alembic>=0.8.10 # MIT
|
|
Babel!=2.4.0,>=2.3.4 # BSD
|
|
falcon>=1.1.0 # Apache-2.0
|
|
jsonschema>=3.2.0 # MIT
|
|
iso8601>=0.1.11 # MIT
|
|
keystonemiddleware>=4.17.0 # Apache-2.0
|
|
msgpack>=0.5.1 # Apache-2.0
|
|
python-memcached>=1.56 # PSF
|
|
python-swiftclient>=3.2.0 # Apache-2.0
|
|
WebOb>=1.7.1 # MIT
|
|
stevedore>=1.20.0 # Apache-2.0
|
|
six>=1.10.0 # MIT
|
|
oslo.cache>=1.26.0 # Apache-2.0
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.context>=2.19.2 # Apache-2.0
|
|
oslo.db>=4.27.0 # Apache-2.0
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.messaging>=5.29.0 # Apache-2.0
|
|
oslo.reports>=1.18.0 # 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
|
|
oslo.policy>=1.30.0 # Apache-2.0
|
|
osprofiler>=1.4.0 # Apache-2.0
|
|
SQLAlchemy!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8,>=1.0.10 # MIT
|
|
autobahn>=0.17.1 # MIT License
|
|
requests>=2.14.2 # Apache-2.0
|
|
futurist>=1.2.0 # Apache-2.0
|