oslo.messaging/requirements-py3.txt

46 lines
1.4 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.
oslo.config>=1.11.0 # Apache-2.0
oslo.context>=0.2.0 # Apache-2.0
oslo.serialization>=1.4.0 # Apache-2.0
oslo.utils>=1.4.0 # Apache-2.0
oslo.i18n>=1.5.0 # Apache-2.0
stevedore>=1.5.0 # Apache-2.0
# for jsonutils
six>=1.9.0
# FIXME(markmc): remove this when the drivers no longer
# import eventlet
eventlet>=0.17.3
# for the routing notifier
PyYAML>=3.1.0
# rabbit driver is the default
# we set the amqp version to ensure heartbeat works
amqp>=1.4.0
kombu>=3.0.7
# middleware
oslo.middleware>=1.2.0,!=2.0.0 # Apache-2.0
# FIXME: concurrent.futures is part of the Python stdlib since Python 3.2,
# but the requirements is still needed because of a bug in tox:
# https://bitbucket.org/hpk42/tox/issue/236/tox-must-create-the-source-distribution
#
# Tox builds a source distribution with "python setup.py sdist" which uses
# requirements.txt even if tox wants to build the py34 virtual environment.
# As a consequence, oslo.messaging.egg_info/requires.txt contains futures
# and oslo_messaging.tests.test_opts.OptsTestCase.test_entry_point fails.
#
# for the futures based executor
futures>=3.0
# needed by the aioeventlet executor
aioeventlet>=0.4
trollius>=1.0