openstack/horizon
Code Issues Proposed changes

Merge "Remove old excludes"

Browse Source
This commit is contained in:
Zuul 2024-05-01 05:43:47 +00:00 committed by Gerrit Code Review
commit 64eddcd3f5
3 changed files with 3 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/requirements.txt
View File

@ -1,13 +1,6 @@
# 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.
openstackdocstheme>=2.2.0 # Apache-2.0 openstackdocstheme>=2.2.0 # Apache-2.0
reno>=3.1.0 # Apache-2.0 reno>=3.1.0 # Apache-2.0
sphinx>=2.0.0,!=2.1.0 # BSD sphinx>=2.0.0 # BSD
doc8>=0.8.1 # Apache-2.0 doc8>=0.8.1 # Apache-2.0
# The below is rewquired to build testing module reference # The below is rewquired to build testing module reference

12
requirements.txt
View File

@ -1,16 +1,6 @@
# Note: Requirements lower bounds listed here are our best effort to keep them up to # Note: Requirements lower bounds listed here are our best effort to keep them up to
# date but we do not test them so there is no guarantee of having them all correct. # date but we do not test them so there is no guarantee of having them all correct.
# if you find any incorrect lower bounds, let us know or propose a fix. # if you find any incorrect lower bounds, let us know or propose a fix.
# 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>=5.5.0 # Apache-2.0 pbr>=5.5.0 # Apache-2.0
# Horizon Core Requirements # Horizon Core Requirements
@ -32,7 +22,7 @@ oslo.serialization>=4.3.0 # Apache-2.0
oslo.upgradecheck>=1.5.0 # Apache-2.0 oslo.upgradecheck>=1.5.0 # Apache-2.0
oslo.utils>=4.12.0 # Apache-2.0 oslo.utils>=4.12.0 # Apache-2.0
osprofiler>=3.4.2 # Apache-2.0 osprofiler>=3.4.2 # Apache-2.0
pymongo!=3.1,>=3.0.2 # Apache-2.0 pymongo>=3.0.2 # Apache-2.0
pyScss>=1.4.0 # MIT License pyScss>=1.4.0 # MIT License
python-cinderclient>=8.0.0 # Apache-2.0 python-cinderclient>=8.0.0 # Apache-2.0
python-glanceclient>=2.8.0 # Apache-2.0 python-glanceclient>=2.8.0 # Apache-2.0

10
test-requirements.txt
View File

@ -1,12 +1,4 @@
# The order of packages is significant, because pip processes them in the order coverage>=4.0 # Apache-2.0
# 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.
#
coverage!=4.4,>=4.0 # Apache-2.0
freezegun>=0.3.15 # Apache-2.0 freezegun>=0.3.15 # Apache-2.0
nodeenv>=0.9.4 # BSD nodeenv>=0.9.4 # BSD
pytest>=5.3.5 # MIT pytest>=5.3.5 # MIT