Merge "Remove note about old pip's behavior"
This commit is contained in:
@@ -1,7 +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.
|
||||
|
||||
openstackdocstheme>=2.2.1 # Apache-2.0
|
||||
sphinx>=2.0.0,!=2.1.0 # BSD
|
||||
reno>=3.1.0 # Apache-2.0
|
||||
|
||||
@@ -1,16 +1,3 @@
|
||||
# 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
|
||||
|
||||
Reference in New Issue
Block a user