2dbf39295c
Having the data validation happening inside the unit tests makes understanding requirement update failures confusing because the output is hard to read and does not explain what the error actually is. Move the checks to their own command and set up a tox env to run it. A separate patch in project-config will add a new job for the repository. Address the dedent comment from https://review.openstack.org/#/c/204181/3/openstack_requirements/tests/test_requirement.py,cm Add a test to ensure that all items in global-requirements.txt are also listed in either upper-constraints.txt or blacklist.txt. Ignore a few items that we don't know how to constrain yet. Add a test to ensure that items in blacklist.txt are not in upper-constraints.txt. Change-Id: Icb717b0f36afb6ea29f50bc6935917dddf47fd4c
30 lines
968 B
INI
30 lines
968 B
INI
[metadata]
|
|
name = openstack.requirements
|
|
summary = OpenStack Python Dependencies
|
|
description-file =
|
|
README.rst
|
|
author = OpenStack
|
|
author-email = openstack-dev@lists.openstack.org
|
|
home-page = http://www.openstack.org/
|
|
classifier =
|
|
Environment :: OpenStack
|
|
Intended Audience :: Information Technology
|
|
Intended Audience :: System Administrators
|
|
License :: OSI Approved :: Apache Software License
|
|
Operating System :: POSIX :: Linux
|
|
Programming Language :: Python
|
|
Programming Language :: Python :: 2
|
|
Programming Language :: Python :: 2.7
|
|
Programming Language :: Python :: 2.6
|
|
|
|
[files]
|
|
packages =
|
|
openstack_requirements
|
|
|
|
[entry_points]
|
|
console_scripts =
|
|
edit-constraints = openstack_requirements.cmds.edit_constraint:main
|
|
generate-constraints = openstack_requirements.cmds.generate:main
|
|
update-requirements = openstack_requirements.cmds.update:main
|
|
validate-constraints = openstack_requirements.cmds.validate:main
|