15afe9c6a5
Django 1.11 ends its extended support in April 2020 (which is before Ussuri release), so horizon drops Django 1.11 support in Ussuri. tox envs for non-primary Django versions are no longer needed in tox.ini as testing environments for non-primary Django versions are setup in the zuul jobs now. horizon>=17.1.0 is required to use Django 2.2. requirements.txt and lower-constraints.txt are updated accordingly. for more info. please refer [1]. This patch also drop django-babel as horizon already swiched from django-babel to enmerkar. congress-dashboard requirement.txt needs to sync the change to fix gate failure. enmerkar, a successor of django-babel will be installed via horizon, so we don't need to have it in requirements.txt explicitly. Depends-On: https://review.opendev.org/#/c/700733/ [1] https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin Change-Id: I105be486e98b856839214e72a363674cd5c23b9f
15 lines
659 B
Plaintext
15 lines
659 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.
|
|
# Order matters to the pip dependency resolver, so sorting this file
|
|
# changes how packages are installed. New dependencies should be
|
|
# added in alphabetical order, however, some dependencies may need to
|
|
# be installed in a specific order.
|
|
#
|
|
# PBR should always appear first
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
django-compressor>=2.0 # MIT
|
|
keystoneauth1>=3.4.0 # Apache-2.0
|
|
python-congressclient<2000,>=1.9.0 # Apache-2.0
|
|
horizon>=17.1.0 # Apache-2.0
|