From 7a3852efb2e5f61842ab53f15158193235828226 Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Tue, 30 Apr 2024 22:47:30 +0900 Subject: [PATCH] Remove old excludes These are detected as errors since the clean up was done[1] in the requirements repository. [1] 314734e938f107cbd5ebcc7af4d9167c11347406 Also remove the note about old pip's behavior because the resolver in recent pip no longer requires specific order. Change-Id: I5355c3fa692df22f4dc0c8aeac4fb12bae6dfec6 --- doc/requirements.txt | 5 +---- requirements.txt | 7 ++----- test-requirements.txt | 5 +---- 3 files changed, 4 insertions(+), 13 deletions(-) diff --git a/doc/requirements.txt b/doc/requirements.txt index a7d55fa86..7993d4722 100644 --- a/doc/requirements.txt +++ b/doc/requirements.txt @@ -1,7 +1,4 @@ -# 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 reno>=3.1.0 # Apache-2.0 -sphinx>=2.0.0,!=2.1.0 # BSD +sphinx>=2.0.0 # BSD sphinxcontrib-apidoc>=0.2.0 # BSD diff --git a/requirements.txt b/requirements.txt index 3c4010cb3..77be99f66 100644 --- a/requirements.txt +++ b/requirements.txt @@ -2,12 +2,9 @@ # date but we do not test them so no guarantee of having them all correct. 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. -pbr!=2.1.0,>=2.0.0 # Apache-2.0 +pbr>=2.0.0 # Apache-2.0 platformdirs>=3 # MIT License -cliff!=2.9.0,>=2.8.0 # Apache-2.0 +cliff>=2.8.0 # Apache-2.0 dogpile.cache>=0.8.0 # BSD jsonschema>=3.2.0 # MIT keystoneauth1>=3.11.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 7b19faea6..de1c8817f 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,7 +1,4 @@ -# 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. -coverage!=4.4,>=4.0 # Apache-2.0 +coverage>=4.0 # Apache-2.0 fixtures>=3.0.0 # Apache-2.0/BSD requests-mock>=1.2.0 # Apache-2.0 oslotest>=3.2.0 # Apache-2.0