openstack/neutron
Code Issues Proposed changes

Add a tox requirements target

Browse Source 
In some other repos you can run 'tox -e requirements' and
run the requirements checks, which is useful when adding
or changing requirements.  Add it to tox.ini and fix a
python2 warning it noticed as well.

Change-Id: I8caa7f755d1276ffe581583a1ea61bb5f0473924
This commit is contained in:
Brian Haley 2019-12-11 13:21:42 -05:00
parent 3ad5ad02c9
commit ed26c606c1
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/requirements.txt
View File

@ -1,7 +1,6 @@
# 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.
sphinx!=1.6.6,!=1.6.7,>=1.6.2,<2.0.0;python_version=='2.7' # BSD
sphinx!=1.6.6,!=1.6.7,!=2.1.0,>=1.6.2;python_version>='3.4' # BSD
openstackdocstheme>=1.30.0 # Apache-2.0
oslotest>=3.2.0 # Apache-2.0

7
tox.ini
View File

@ -209,3 +209,10 @@ deps =
-c{toxinidir}/lower-constraints.txt
-r{toxinidir}/test-requirements.txt
-r{toxinidir}/requirements.txt
[testenv:requirements]
deps =
-egit+https://opendev.org/openstack/requirements#egg=openstack-requirements
whitelist_externals = sh
commands =
sh -c '{envdir}/src/openstack-requirements/playbooks/files/project-requirements-change.py --req {envdir}/src/openstack-requirements --local {toxinidir} master'