blazar-dashboard/requirements.txt
Pierre Riteau fa1a31a448 Drop lower-constraints.txt and its testing
As discussed in TC PTG [1] and TC resolution [2], we are dropping the
lower-constraints.txt file and its testing. We will keep lower bounds
in the requirements.txt file but with a note that these are not tested
lower bounds and we try our best to keep them updated.

[1] https://etherpad.opendev.org/p/tc-zed-ptg#L326
[2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html

Change-Id: Ib425c4791477803224460b536fe88c506e36d623
2023-09-14 18:49:00 +02:00

18 lines
832 B
Plaintext

# 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. 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!=2.1.0,>=2.0.0 # Apache-2.0
python-blazarclient>=1.0.1 # Apache-2.0
horizon>=17.1.0 # Apache-2.0