27 lines
1.1 KiB
Plaintext
27 lines
1.1 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.
|
|
|
|
stestr>=1.0.0 # Apache-2.0
|
|
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
python-subunit>=1.0.0 # Apache-2.0/BSD
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
os-testr>=1.0.0 # Apache-2.0
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
ddt>=1.0.1 # MIT
|
|
|
|
# Due to the nature of libvirt-python package, in DevStack we use the one
|
|
# provided in the distro alongside libvirtd - to ensure the two are compatible,
|
|
# and also to avoid the pip error when it tries to uninstall the distro version
|
|
# (installed in such a way for Nova in DevStack).
|
|
# Do note libvirt-python is used only for instance-oriented monitors, so, e.g.,
|
|
# it is not used by any host monitor.
|
|
# TODO(yoctozepto): Refactor code to not require libvirt-python for unit tests,
|
|
# basically following how it is handled in nova-compute and ceilometer-compute.
|
|
libvirt-python>=6.0.0 # LGPLv2+
|