ab4c9fd15c
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: I097b2d0349083cad1908db8dc25a33d9ad492adb
17 lines
613 B
Plaintext
17 lines
613 B
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.
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
stevedore>=1.20.0 # Apache-2.0
|
|
eventlet!=0.18.3,!=0.20.1,>=0.18.2 # MIT
|
|
six>=1.10.0 # MIT
|
|
|
|
jsonschema>=3.2.0 # MIT
|
|
keystoneauth1>=3.4.0 # Apache-2.0
|
|
python-keystoneclient>=3.8.0 # Apache-2.0
|
|
requests>=2.14.2 # Apache-2.0
|