From 7e1db552456f5963632445ee91e63fc74ed12923 Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Mon, 23 Jul 2018 11:52:17 -0500 Subject: [PATCH] Add reno to requirements Our HACKING documentation instructs developers to use: "tox -e venv -- reno new " to create new release notes. We did not add reno to our requirements though, so attempting to run "tox -e venv -- reno" fails with the command not found. This adds reno to our requirements so they get installed in the venv. Change-Id: Ie888297098e9380587769affad1a8ca9a6dfe5bc Signed-off-by: Sean McGinnis --- lower-constraints.txt | 1 + test-requirements.txt | 1 + 2 files changed, 2 insertions(+) diff --git a/lower-constraints.txt b/lower-constraints.txt index 810beddb9..73d8a64c1 100644 --- a/lower-constraints.txt +++ b/lower-constraints.txt @@ -47,6 +47,7 @@ python-mimeparse==1.6.0 python-subunit==1.0.0 pytz==2013.6 PyYAML==3.12 +reno==2.5.0 requests-mock==1.2.0 requests==2.14.2 rfc3986==0.3.1 diff --git a/test-requirements.txt b/test-requirements.txt index e16fdd596..a62a30869 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -7,6 +7,7 @@ coverage!=4.4,>=4.0 # Apache-2.0 ddt>=1.0.1 # MIT fixtures>=3.0.0 # Apache-2.0/BSD mock>=2.0.0 # BSD +reno>=2.5.0 # Apache-2.0 requests-mock>=1.2.0 # Apache-2.0 tempest>=17.1.0 # Apache-2.0 testtools>=2.2.0 # MIT