33 lines
837 B
Plaintext
33 lines
837 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.
|
|
# Metrics and style
|
|
hacking<0.11,>=0.10.0
|
|
|
|
# Packaging
|
|
mock>=2.0 # BSD
|
|
|
|
# Backends
|
|
redis>=2.10.0 # MIT
|
|
pymongo!=3.1,>=3.0.2 # Apache-2.0
|
|
websocket-client>=0.32.0 # LGPLv2+
|
|
|
|
# Unit testing
|
|
coverage>=3.6 # Apache-2.0
|
|
ddt>=1.0.1 # MIT
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
python-subunit>=0.0.18 # Apache-2.0/BSD
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testtools>=1.4.0 # MIT
|
|
|
|
# Documentation
|
|
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD
|
|
oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0
|
|
openstack-doc-tools>=0.23 # Apache-2.0
|
|
oslotest>=1.10.0 # Apache-2.0
|
|
reno>=1.6.2 # Apache2
|
|
os-api-ref>=0.1.0 # Apache-2.0
|
|
|
|
# Tempest
|
|
tempest>=11.0.0 # Apache-2.0
|