oslo.messaging/test-requirements.txt
Kirill Bespalov 0991a696ca Add reno for releasenotes management
An initial patch to add reno and create a base directory for
release notes

Change-Id: If393d865f3f054379a713d0e9f905d43b2faeccb
2016-05-19 17:14:31 +03:00

43 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.
# Hacking already pins down pep8, pyflakes and flake8
hacking<0.11,>=0.10.0
discover # BSD
fixtures<2.0,>=1.3.1 # Apache-2.0/BSD
mock>=1.2 # BSD
mox3>=0.7.0 # Apache-2.0
python-subunit>=0.0.18 # Apache-2.0/BSD
testrepository>=0.0.18 # Apache-2.0/BSD
testscenarios>=0.4 # Apache-2.0/BSD
testtools>=1.4.0 # MIT
oslotest>=1.10.0 # Apache-2.0
# for test_matchmaker_redis
redis>=2.10.0 # MIT
# for test_impl_zmq
pyzmq>=14.3.1 # LGPL+BSD
# for test_impl_kafka
kafka-python<1.0.0,>=0.9.5 # Apache-2.0
# when we can require tox>= 1.4, this can go into tox.ini:
# [testenv:cover]
# deps = {[testenv]deps} coverage
coverage>=3.6 # Apache-2.0
# this is required for the docs build jobs
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD
oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0
reno>=1.6.2 # Apache2
# AMQP 1.0 support depends on the Qpid Proton AMQP 1.0
# development libraries.
pyngus>=2.0.0 # Apache-2.0
# Bandit security code scanner
bandit>=1.0.1 # Apache-2.0