4f807b8c60
For people installing released shade from pip and then trying to use it somehow through entrypoints, 1.20.0 is currently broken because of some transitive dependencies, ordering issues and conflicting exclusion ranges. While this is by no means a comprehensive or sustainable solution to the problem, it does unbreak the end users currently broken and is not terribly onerous. Both of these additions are tracked in g-r and both can be removed when the dependencies that pull in conflicting ranges of things are removed. Change-Id: I6a4a1ab5ab109f0650873201868e0f1c4d09c564
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
# 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
|
|
|
|
munch>=2.1.0 # MIT
|
|
decorator>=3.4.0 # BSD
|
|
jmespath>=0.9.0 # MIT
|
|
jsonpatch>=1.1 # BSD
|
|
ipaddress>=1.0.7;python_version<'3.3' # PSF
|
|
os-client-config>=1.22.0 # Apache-2.0
|
|
# These two are here to prevent issues with version pin mismatches from our
|
|
# client library transitive depends.
|
|
# Babel can be removed when ironicclient is removed (because of openstackclient
|
|
# transitive depend)
|
|
Babel>=2.3.4,!=2.4.0 # BSD
|
|
# requests can be removed when designateclient is removed
|
|
requests>=2.10.0,!=2.12.2,!=2.13.0 # Apache-2.0
|
|
requestsexceptions>=1.2.0 # Apache-2.0
|
|
six>=1.9.0 # MIT
|
|
futures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD
|
|
|
|
keystoneauth1>=2.18.0 # Apache-2.0
|
|
netifaces>=0.10.4 # MIT
|
|
python-novaclient>=7.1.0 # Apache-2.0
|
|
python-keystoneclient>=3.8.0 # Apache-2.0
|
|
python-cinderclient>=2.0.1 # Apache-2.0
|
|
python-neutronclient>=5.1.0 # Apache-2.0
|
|
python-ironicclient>=1.11.0 # Apache-2.0
|
|
python-designateclient>=1.5.0 # Apache-2.0
|
|
|
|
dogpile.cache>=0.6.2 # BSD
|