openstack/oslo.policy
Code Issues Proposed changes

Remove old excludes

Browse Source 
These are detected as errors since the clean up was done[1] in
the requirements repository.

[1] 314734e938f107cbd5ebcc7af4d9167c11347406

Change-Id: Ib3b1ffea6b7f1609f2fa92fce598b5697a96de2c
This commit is contained in:
Takashi Kajinami 2024-05-01 11:38:34 +09:00
parent f2627a8975
commit db16e6832b
3 changed files with 4 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/requirements.txt
View File

@ -1,9 +1,5 @@
# 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.
openstackdocstheme>=2.2.0 # Apache-2.0
sphinx>=2.0.0,!=2.1.0 # BSD
sphinx>=2.0.0 # BSD
sphinxcontrib-apidoc>=0.2.0 # BSD
reno>=3.1.0 # Apache-2.0

6
requirements.txt
View File

@ -1,12 +1,8 @@
# 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.
requests>=2.14.2 # Apache-2.0
oslo.config>=6.0.0 # Apache-2.0
oslo.context>=2.22.0 # Apache-2.0
oslo.i18n>=3.15.3 # Apache-2.0
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
oslo.serialization>=2.18.0 # Apache-2.0
PyYAML>=5.1 # MIT
stevedore>=1.20.0 # Apache-2.0
oslo.utils>=3.40.0 # Apache-2.0

8
test-requirements.txt
View File

@ -1,11 +1,7 @@
# 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.
oslotest>=3.2.0 # Apache-2.0
requests-mock>=1.2.0 # Apache-2.0
stestr>=2.0.0 # Apache-2.0
sphinx>=2.0.0,!=2.1.0 # BSD
sphinx>=2.0.0 # BSD
# computes code coverage percentages
coverage!=4.4,>=4.0 # Apache-2.0
coverage>=4.0 # Apache-2.0