Fix venv use in requirements propose_update.sh

This script creates a virtualenv to run a requirements script to update
constraints. virtualenv is not globally available anymore. Rather than
trying to call it directly, this now uses tox to set up the virtual
environment.

Change-Id: If00afb50c37b45aefbb45070da4efef3e43e62b2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis 2020-06-23 07:51:44 -05:00
parent 83aa828d93
commit bfc06ae553
No known key found for this signature in database
GPG Key ID: CE7EE4BFAF8D70C8
1 changed files with 2 additions and 3 deletions

View File

@ -32,9 +32,8 @@ elif [ "$OWN_PROJECT" == "requirements-constraints" ] ; then
INITIAL_COMMIT_MSG="Updated from generate-constraints"
TOPIC="openstack/requirements/constraints"
PROJECTS=openstack/requirements
VENV=$(mktemp -d)
trap "rm -rf $VENV" EXIT
virtualenv -p python3 $VENV
tox -re venv --notest
VENV=$(readlink -f .tox/venv)
$VENV/bin/pip install -e .
function update {
$VENV/bin/generate-constraints -b blacklist.txt -p /usr/bin/python3.6 \