openstack/oslo.messaging
Code Issues Proposed changes
709ee7989d
oslo.messaging/tox.ini

123 lines
4.2 KiB
INI
Raw Normal View History

Add oslo.messaging project infrastructure
2013-06-15 07:49:11 +01:00
[tox]
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
minversion = 2.0
Remove references to Python 3.4 Now that there exists only a gate job for Python 3.5 and not 3.4, we should remove those references to the 3.4 that is untested. Change-Id: I2a00ead626d9eced96487ee82b5d7857126d8355
2017-01-09 10:08:07 -08:00
envlist = py35,py27,pep8,bandit
Add oslo.messaging project infrastructure
2013-06-15 07:49:11 +01:00
[testenv]
Convert to oslo.test bp graduate-oslo-test Change-Id: Iff1eebac011dab26468a7f1475b5c36b0bb2a7d2
2014-02-26 17:05:07 -08:00
setenv =
VIRTUAL_ENV={envdir}
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
BRANCH_NAME=master
CLIENT_NAME=oslo.messaging
Fix typo passend should be passenv Looks like a typo. It should be passenv as mentioned in tox docs: https://testrun.org/tox/latest/config.html Change-Id: I14a18ec5b6c53ad4931b144ef66916563047cde6
2016-03-21 17:36:11 -04:00
passenv = OS_*
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
ZUUL_CACHE_DIR
REQUIREMENTS_PIP_LOCATION
install_command = {toxinidir}/tools/tox_install.sh {env:UPPER_CONSTRAINTS_FILE:https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt} {opts} {packages}
cleanup tox.ini * Remove requirements.txt from deps, as this is already added automatically Change-Id: I696dd69ba1d59ab026180e8e3cb864fe37442e10
2015-11-14 23:06:55 -05:00
deps = -r{toxinidir}/test-requirements.txt
Add oslo.messaging project infrastructure
2013-06-15 07:49:11 +01:00
commands = python setup.py testr --slowest --testr-args='{posargs}'
[testenv:pep8]
commands = flake8
make pep8 faster This builds a stripped down tox target for pep8 that doesn't need a giant venv with all the things. Works fast and lean, and makes julien fries. Change-Id: Id5b7671fb7f2b8cbf88745fd12f9238b3c0bb2dd
2015-11-19 14:09:38 -05:00
deps = hacking<0.11,>=0.10.0
Add oslo.messaging project infrastructure
2013-06-15 07:49:11 +01:00
[testenv:cover]
commands =
Fix coverage report generation Coverage is a little bit confused by oslo.messaging as the pypi package name. So we have to be explicit here or we get no data collection. Adding a .coveragerc helps give the report more context as we don't care about coverage in the tests or oslo-incubator. Change-Id: I3d24187890efd7aecad7fcb7a2974b87e89ef6ff
2015-03-12 13:45:11 -07:00
python setup.py test --coverage --coverage-package-name=oslo_messaging --testr-args='{posargs}'
Add oslo.messaging project infrastructure
2013-06-15 07:49:11 +01:00
[testenv:venv]
commands = {posargs}
Add 'docs' tox environment To make it easy to build docs with 'tox -e docs'. Change-Id: Idd47c617196b25539b6b1fc88fac0a45b7fc0911
2014-06-26 06:32:27 +01:00
[testenv:docs]
tox: Build docs with Python 2.7 The 'list-modules' directive used in some docs does not appear to be Python 3 compatible, yielding the following error: TypeError: unorderable types: NoneType() < str() Simply use Python 2.7 until such a time as someone wants to investigate why this happens. Change-Id: I0be19b056e1c2272df3666626fbd17ec78017bce
2017-03-16 14:57:55 +00:00
basepython = python2.7
Add 'docs' tox environment To make it easy to build docs with 'tox -e docs'. Change-Id: Idd47c617196b25539b6b1fc88fac0a45b7fc0911
2014-06-26 06:32:27 +01:00
commands = python setup.py build_sphinx
Add qpid and amqp 1.0 tox targets This change adds two targets for qpid and amqp to be able to run the functional tests suite on them in gate This also run only functional tests for the functional tox testenv Change-Id: Ibf1db3fe55f82dd6dc02f2e57d73608fcad80d0e
2014-10-22 23:46:48 +02:00
[testenv:py27-func-rabbit]
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
setenv =
{[testenv]setenv}
TRANSPORT_DRIVER=rabbit
tests: allow to override the functionnal tests suite args Change-Id: Ia958b3812be7c51a07734081542f14452c5de658
2016-04-07 10:35:18 +02:00
commands = pifpaf run rabbitmq -- python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
Add qpid and amqp 1.0 tox targets This change adds two targets for qpid and amqp to be able to run the functional tests suite on them in gate This also run only functional tests for the functional tox testenv Change-Id: Ibf1db3fe55f82dd6dc02f2e57d73608fcad80d0e
2014-10-22 23:46:48 +02:00
Add Python 3.5 classifier and venv Now that there is a passing gate job, we can claim support for Python 3.5 in the classifier. This patch also adds the convenience py35 venv. Change-Id: I8871f4e17ab806c00661d0c960a216d0a3fc5449
2016-07-12 16:35:36 +08:00
[testenv:py35-func-rabbit]
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
setenv =
{[testenv]setenv}
TRANSPORT_DRIVER=rabbit
Add Python 3.5 classifier and venv Now that there is a passing gate job, we can claim support for Python 3.5 in the classifier. This patch also adds the convenience py35 venv. Change-Id: I8871f4e17ab806c00661d0c960a216d0a3fc5449
2016-07-12 16:35:36 +08:00
basepython = python3.5
commands = pifpaf run rabbitmq -- python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
Implements rabbit-pika driver In this patch new driver implementation added and registered in setup.cfg, integrated ith tox functional tests. Implements: bp rabbit-pika Depends-On: I7bda78820e657b1e97bf888d4065a917eb317cfb Change-Id: I40842a03ce73d171644c362e3abfca2990aca58a
2015-10-01 18:53:17 +03:00
[testenv:py27-func-pika]
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
setenv =
{[testenv]setenv}
TRANSPORT_DRIVER=pika
tests: allow to override the functionnal tests suite args Change-Id: Ia958b3812be7c51a07734081542f14452c5de658
2016-04-07 10:35:18 +02:00
commands = pifpaf run rabbitmq -- python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
Implements rabbit-pika driver In this patch new driver implementation added and registered in setup.cfg, integrated ith tox functional tests. Implements: bp rabbit-pika Depends-On: I7bda78820e657b1e97bf888d4065a917eb317cfb Change-Id: I40842a03ce73d171644c362e3abfca2990aca58a
2015-10-01 18:53:17 +03:00
kafka separate unit/functionnal tests The kafka functional tests don't use our setup framework but hardcode the kafka url. The kafka driver is broken and currently try to be loaded with other driver tests (and break py3 gate job). This change remove the hardcoded stuff and uses the normal functional tests setup to check kafka. This avoids kafka tests to be ran on other driver tests job. It also creates the tox target for functional tests and use pifpaf to setup kafka. As today, the functional test suite doesn't work all. Change-Id: Ie6af35321905a04b38e549bf7268dd40543d9e3a
2016-11-30 15:37:32 +01:00
[testenv:py27-func-kafka]
setenv =
{[testenv]setenv}
TRANSPORT_DRIVER=kafka
tests: don't run functional tests in parallel kafka doesn't play well with //, each times a new partition/topic is created, kafka rebalances things across brokers and messages are not delivered at the expected time. So this change disable the parallelizism for functional tests for kafka only. Change-Id: Ia497334efcd4685850ac1529a7fc38073dae7cd1
2016-12-13 21:54:42 +01:00
OS_GROUP_REGEX=oslo_messaging.tests.functional
Moving driver to new kafka-python version Currently Kafka driver for an oslo.messaging uses kafka-python==0.9.5 and mostly broken. This package version supports only low level Kafka producer and consumer API which are marked as deprecated now [1]. Using of these interfaces bring a big concern to the message processing, because current KafkaConsumer has not any consuming coordination. This fact causes a message duplication for the several consumers of one topic. This behavior is specific to Ceilometer and services which read and process notifications from other services. New version of kafka-python allows to use async thread safe message producers and coordinated consumers [1]. [1] http://kafka-python.readthedocs.io/en/master/changelog.html#feb-15-2016 The driver is currently experimental, python-kafka<1.0.0 API have major issue described above that can't make the oslo.messaging driver works, so we prefer having a working driver with a non-synced dependencies, that the reverse. Co-Authored-By: Mehdi Abaakouk <sileht@redhat.com> Change-Id: I29862ed7bf56b9d8878fa8e9fb1cbd9d643908a4
2016-06-21 14:57:17 +03:00
kafka-python>=1.3.1
kafka separate unit/functionnal tests The kafka functional tests don't use our setup framework but hardcode the kafka url. The kafka driver is broken and currently try to be loaded with other driver tests (and break py3 gate job). This change remove the hardcoded stuff and uses the normal functional tests setup to check kafka. This avoids kafka tests to be ran on other driver tests job. It also creates the tox target for functional tests and use pifpaf to setup kafka. As today, the functional test suite doesn't work all. Change-Id: Ie6af35321905a04b38e549bf7268dd40543d9e3a
2016-11-30 15:37:32 +01:00
commands = {toxinidir}/setup-test-env-kafka.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
Add qpid and amqp 1.0 tox targets This change adds two targets for qpid and amqp to be able to run the functional tests suite on them in gate This also run only functional tests for the functional tox testenv Change-Id: Ibf1db3fe55f82dd6dc02f2e57d73608fcad80d0e
2014-10-22 23:46:48 +02:00
[testenv:py27-func-amqp1]
[AMQP 1.0] Update setup test environment dispatch router backend This commit updates the setup environment for the driver functional tests to support either a qpidd (broker) or qdrouterd (router) backend. This patch: * configures and runs either qpidd or qdrouterd backend * removes support of older qpidd versions * skips batch notification test for qdrouterd backend Change-Id: Ifcdc187bae4a28dd29c1faa73e239d7e4d77015d
2016-08-25 15:52:18 -04:00
setenv =
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
{[testenv]setenv}
[AMQP 1.0] Update setup test environment dispatch router backend This commit updates the setup environment for the driver functional tests to support either a qpidd (broker) or qdrouterd (router) backend. This patch: * configures and runs either qpidd or qdrouterd backend * removes support of older qpidd versions * skips batch notification test for qdrouterd backend Change-Id: Ifcdc187bae4a28dd29c1faa73e239d7e4d77015d
2016-08-25 15:52:18 -04:00
TRANSPORT_URL=amqp://stackqpid:secretqpid@127.0.0.1:65123//
AMQP1_BACKEND=qpidd
ENVNAME={envname}
WORKDIR={toxworkdir}
Move legacy zuulv3 tests into oslo.messaging repo Next step will be to re-write these for zuulv3 Change-Id: I2f6a8432e037f75d6abee3bc977933a310a4a2c7
2017-10-06 13:42:05 -04:00
commands = {toxinidir}/tools/setup-test-env-amqp1.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
Add Python 3.4 functional tests for AMQP 1.0 driver Change-Id: Ieead11641df3e711555420517e9668258a79410b Closes-Bug: #1598209
2016-07-01 13:44:25 -04:00
Add Python 3.5 classifier and venv Now that there is a passing gate job, we can claim support for Python 3.5 in the classifier. This patch also adds the convenience py35 venv. Change-Id: I8871f4e17ab806c00661d0c960a216d0a3fc5449
2016-07-12 16:35:36 +08:00
[testenv:py35-func-amqp1]
basepython = python3.5
[AMQP 1.0] Update setup test environment dispatch router backend This commit updates the setup environment for the driver functional tests to support either a qpidd (broker) or qdrouterd (router) backend. This patch: * configures and runs either qpidd or qdrouterd backend * removes support of older qpidd versions * skips batch notification test for qdrouterd backend Change-Id: Ifcdc187bae4a28dd29c1faa73e239d7e4d77015d
2016-08-25 15:52:18 -04:00
setenv =
Add Constraints support Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.messaging. Change-Id: I8be883215f27abb58d15b85e8542cbdf32000bac
2016-11-08 14:15:10 +11:00
{[testenv]setenv}
[AMQP 1.0] Update setup test environment dispatch router backend This commit updates the setup environment for the driver functional tests to support either a qpidd (broker) or qdrouterd (router) backend. This patch: * configures and runs either qpidd or qdrouterd backend * removes support of older qpidd versions * skips batch notification test for qdrouterd backend Change-Id: Ifcdc187bae4a28dd29c1faa73e239d7e4d77015d
2016-08-25 15:52:18 -04:00
TRANSPORT_URL=amqp://stackqpid:secretqpid@127.0.0.1:65123//
AMQP1_BACKEND=qpidd
ENVNAME={envname}
WORKDIR={toxworkdir}
Move legacy zuulv3 tests into oslo.messaging repo Next step will be to re-write these for zuulv3 Change-Id: I2f6a8432e037f75d6abee3bc977933a310a4a2c7
2017-10-06 13:42:05 -04:00
commands = {toxinidir}/tools/setup-test-env-amqp1.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
Add Python 3.5 classifier and venv Now that there is a passing gate job, we can claim support for Python 3.5 in the classifier. This patch also adds the convenience py35 venv. Change-Id: I8871f4e17ab806c00661d0c960a216d0a3fc5449
2016-07-12 16:35:36 +08:00
tox: rename zeromq target The current zeromq target name are too long and reach the limitation of 127 chars of the sheband of the virtualenv binary. A target name must not be more than 22 chars to run in gate with the tox job template. This renames them to a shorter one. It also creates aliases for the legacy jobs that we will remove when the tox jobs are ready. Change-Id: I5cbc368e7ea252f8c0c949c8e7ee3a70a560db22
2016-12-15 09:42:01 +01:00
[testenv:py27-func-zmq]
tests: allow to override the functionnal tests suite args Change-Id: Ia958b3812be7c51a07734081542f14452c5de658
2016-04-07 10:35:18 +02:00
commands = {toxinidir}/setup-test-env-zmq.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
Gate functionnal testing improvements set DEVSTACK_GATE_NO_SERVICES=1 to not setup a whole openstack when we need only a messaging broker. Add of the zeromq gate job. Fix the amqp1.0 password Change-Id: If1332d97c4d4e92bf920fed4de2795461d9feb22
2015-01-30 09:00:00 +01:00
[zmq] Support py35 testenv Change-Id: If33583d1f89e6068b232fe09f1483c979b0ef84c
2017-01-11 14:03:09 +02:00
[testenv:py35-func-zmq]
commands = {toxinidir}/setup-test-env-zmq.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
[zmq] Use more stable configuration in voting job Use static direct connections as voting job for zmq Change-Id: I921317987dfccbd03b8c8c68fc1a169b6a8100c3
2017-01-16 10:09:40 +02:00
[testenv:py27-func-zmq-dyn]
commands = {toxinidir}/setup-test-env-zmq-direct-dynamic.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
[zmq] Restore static direct connections Restore static direct connections which may be useful for services running RPC on controllers only and talking to agents via other means (ssh for example). Change-Id: Icbe45978cb4a8ba5db74e5593ea7be23cba3f44e
2016-12-24 00:53:48 +02:00
tox: rename zeromq target The current zeromq target name are too long and reach the limitation of 127 chars of the sheband of the virtualenv binary. A target name must not be more than 22 chars to run in gate with the tox job template. This renames them to a shorter one. It also creates aliases for the legacy jobs that we will remove when the tox jobs are ready. Change-Id: I5cbc368e7ea252f8c0c949c8e7ee3a70a560db22
2016-12-15 09:42:01 +01:00
[testenv:py27-func-zmq-proxy]
[zmq] Cleanup changes to zmq-specific f-tests Change-Id: Icce92106a0a0a07a4f2d19fe8bcd7c2a6fa530c8
2016-10-27 16:46:23 +03:00
commands = {toxinidir}/setup-test-env-zmq-proxy.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
[zmq] Additional configurations for f-tests Extend functional testing to cover all zmq deployment configurations. Change-Id: I03a1bb27a4cca429405a19e9de3ba593bbf1db63
2016-07-04 12:28:57 +03:00
tox: rename zeromq target The current zeromq target name are too long and reach the limitation of 127 chars of the sheband of the virtualenv binary. A target name must not be more than 22 chars to run in gate with the tox job template. This renames them to a shorter one. It also creates aliases for the legacy jobs that we will remove when the tox jobs are ready. Change-Id: I5cbc368e7ea252f8c0c949c8e7ee3a70a560db22
2016-12-15 09:42:01 +01:00
[testenv:py27-func-zmq-pubsub]
[zmq] Cleanup changes to zmq-specific f-tests Change-Id: Icce92106a0a0a07a4f2d19fe8bcd7c2a6fa530c8
2016-10-27 16:46:23 +03:00
commands = {toxinidir}/setup-test-env-zmq-pub-sub.sh python setup.py testr --slowest --testr-args='{posargs:oslo_messaging.tests.functional}'
[zmq] Additional configurations for f-tests Extend functional testing to cover all zmq deployment configurations. Change-Id: I03a1bb27a4cca429405a19e9de3ba593bbf1db63
2016-07-04 12:28:57 +03:00
Add a "bandit" target to tox.ini This will allow us to find potential security issues, such as those fixed by 52e624891fc500c8ab9f3f10ef45258ce740916a and c4a7ac0b653543e8a3ba10060cabdb114fb6672b . Change-Id: I21aa0ca79232784069e55da46920eb43250d8939
2015-10-26 11:01:11 +01:00
[testenv:bandit]
deps = -r{toxinidir}/test-requirements.txt
Explicitly exclude tests from bandit scan Now that the bandit linter runs without a bandit.yaml specified, it should exclude the tests directory similar to how it did before in the bandit.yaml. The reason this has not caused a problem yet is because bandit is still finding a config bandit.yaml in .tox/pep8/etc/bandit/bandit.yaml. But in a newer version of bandit this will not be the case. Change-Id: I6cdceaff2aa906e813f1d1e993f60e66358946ee
2016-03-12 20:03:32 -08:00
commands = bandit -r oslo_messaging -x tests -n5
Add a "bandit" target to tox.ini This will allow us to find potential security issues, such as those fixed by 52e624891fc500c8ab9f3f10ef45258ce740916a and c4a7ac0b653543e8a3ba10060cabdb114fb6672b . Change-Id: I21aa0ca79232784069e55da46920eb43250d8939
2015-10-26 11:01:11 +01:00
Add oslo.messaging project infrastructure
2013-06-15 07:49:11 +01:00
[flake8]
show-source = True
Enable some off-by-default checks Some of the available checks are disabled by default, like: [H106] Don’t put vim configuration in source files [H203] Use assertIs(Not)None to check for None Change-Id: I54b4b950dfcd2ce5a64f38b5d5b5cbe95846a8fa
2017-06-22 11:01:23 +08:00
enable-extensions = H203,H106
Drop H237,H402,H904 in flake8 ignore list In hacking > 0.10.0, we drop H402 and H904, and we have no violations for H237. Change-Id: I17bb1bedc8d93c85f55b7e832885acec4ea24e69
2016-01-15 13:18:34 +08:00
ignore = H405
Enable pep8 on oslo_messaging/tests Somehow we sneaked in a change to ignore pep8 on tests/ directory. Let's cleanup the code and re-enable pep8 Closes-Bug: #1540981 Change-Id: Ic002134a0d0c498991b062466e00068d6ac1f1ab
2016-02-02 11:34:01 -05:00
exclude = .tox,dist,doc,*.egg,build,__init__.py
Synced jsonutils and its dependencies from oslo-incubator The sync includes change that makes sure we get unicode-only dicts from jsonutils no matter which json module implementation is selected. The latest commit in oslo-incubator: - 2e1214b74b5448825d3db26e1308a51b468d3d5c Included commits: * gettextutils.py: - de4adbc4: pep8: fixed multiple violations - 9912e5df: Add API for creating translation functions - 6cc96d05: Fix test_gettextutils on Python 3 - fd33d1ea: Fix gettextutil.Message handling of deep copy failures - 047b2e4e: Change lazy translation to retain complete dict - 6d55e26a: Add support for translating log levels separately * importutils.py: - 1173e469: Remove ValueError when accessing sys.modules - 885828af: Deleted duplicated method in cliutils. * jsonutils.py: - 0d7296f6: Add kwargs to jsonutils.load(s) functions - 18f2bc1b: Enforce unicode json output for jsonutils.load[s]() - 9e5a3938: jsonutils.load() accepts file pointer, not string * timeutils.py: - 250cd88c: Fixed a new pep8 error and a small typo The sync adds new module: strutils. Disabled pep8 import checks for gettextutils to avoid raising 'H302: import only modules.' Change-Id: Ic815ca3df94c33edec9104172048b2cd94b92e3f Closes-Bug: 1314129
2014-06-24 14:11:38 +02:00
[hacking]
import_exceptions =
Move files out of the namespace package Move the public API out of oslo.messaging to oslo_messaging. Retain the ability to import from the old namespace package for backwards compatibility for this release cycle. bp/drop-namespace-packages Co-authored-by: Mehdi Abaakouk <mehdi.abaakouk@enovance.com> Change-Id: Ia562010c152a214f1c0fed767c82022c7c2c52e7
2015-01-02 14:24:57 -05:00
oslo_messaging._i18n
Port to Python 3 This patch enables running all the unit tests (except the qpid ones that are skipped) under Python 3.3 and Python 3.4. Change-Id: I711663b4eedfb3cdeea7e6da7d28c6b92663e611
2014-07-18 15:32:56 +02:00
six.moves
Drop use of 'oslo' namespace package The Oslo libraries have moved all of their code out of the 'oslo' namespace package into per-library packages. The namespace package was retained during kilo for backwards compatibility, but will be removed by the liberty-2 milestone. This change removes the use of the namespace package, replacing it with the new package names. It also adds a local hacking check to prevent regressions, while disabling style checks in the "tests" directory, which will be deleted in a subsequent patch. The patches in the libraries will be put on hold until application patches have landed, or L2, whichever comes first. At that point, new versions of the libraries without namespace packages will be released as a major version update. Please merge this patch, or an equivalent, before L2 to avoid problems with those library releases. Blueprint: remove-namespace-packages https://blueprints.launchpad.net/oslo-incubator/+spec/remove-namespace-packages Change-Id: Iad2ae13c771c99861ca9493c6ab10edcfbd8684a
2015-07-13 21:09:07 +00:00
local-check-factory = oslo_messaging.hacking.checks.factory
Add tox target to find missing requirements Change-Id: I49465a614540c6cc1a0e3f1b448f13db940c784c
2015-06-25 21:25:12 -04:00
[testenv:pip-missing-reqs]
# do not install test-requirements as that will pollute the virtualenv for
# determining missing packages
# this also means that pip-missing-reqs must be installed separately, outside
# of the requirements.txt files
deps = pip_missing_reqs
commands = pip-missing-reqs -d --ignore-module=oslo_messaging* --ignore-file=oslo_messaging/tests/* --ignore-file=tests/ oslo_messaging
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 16:49:51 +03:00
[testenv:releasenotes]
commands = sphinx-build -a -E -W -d releasenotes/build/doctrees -b html releasenotes/source releasenotes/build/html
Add bindep.txt/test-setup.sh to prepare the system Change-Id: I9ac3132c082a31020dc2bf2a778fb5c4c0836c4c
2016-12-01 08:17:18 +01:00
[testenv:bindep]
deps = bindep
commands = bindep {posargs}
Copy Permalink