1ff7748623
from comments when it was last touched it looks like workarounds for unittest2 might be able to be dropped. related: https://github.com/mtreinish/stestr/pull/265 simplify the workaround logic around unittest2 TestCase logic Change-Id: Ibac9d0c2fa2f30605dd44ee58b84946464ea6449
24 lines
818 B
Plaintext
24 lines
818 B
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
|
|
cliff!=2.9.0,>=2.8.0 # Apache-2.0
|
|
jsonschema>=3.2.0 # MIT
|
|
testtools>=2.2.0 # MIT
|
|
paramiko>=2.7.0 # LGPLv2.1+
|
|
cryptography>=2.1 # BSD/Apache-2.0
|
|
netaddr>=0.7.18 # BSD
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.utils>=4.7.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
PyYAML>=3.12 # MIT
|
|
python-subunit>=1.0.0 # Apache-2.0/BSD
|
|
stevedore>=1.20.0 # Apache-2.0
|
|
PrettyTable>=0.7.1 # BSD
|
|
urllib3>=1.21.1 # MIT
|
|
debtcollector>=1.2.0 # Apache-2.0
|