openstack/blazar
Code Issues Proposed changes

Remove note about old pip's behavior

Browse Source 
Recent versions of pip no longer requires that the requirements are
listed in specific orders and can resolve dependencies automatically.

Change-Id: Icb4310abaf3bf85777d1e4ea2a885f22b684496b
Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
This commit is contained in:
Takashi Kajinami
2026-01-23 00:44:55 +09:00
parent 3e7cf24571
commit 068a3c5445
2 changed files with 0 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
requirements.txt
-4
View File
@@ -1,10 +1,6 @@
# Requirements lower bounds listed here are our best effort to keep them up to
# 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
alembic>=0.9.6 # MIT
test-requirements.txt
-3
View File
@@ -1,6 +1,3 @@
# 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.
hacking>=7.0.0,<7.1.0 # Apache-2.0
ddt>=1.0.1 # MIT