From b59a59da354233af247b611f616894484616cd10 Mon Sep 17 00:00:00 2001
From: Andreas Jaeger <aj@suse.com>
Date: Sun, 7 Jun 2020 08:20:58 +0200
Subject: [PATCH] Use python 3 venv for generate-constraints

With change I15d451f6a832b2e698b28e7351a36ef7aea92abe
generate-constraints needs python 3, setup the venv using python 3.

Change-Id: I3dba35267dc6f344ad27910c7dc18c1a33abf4ba
---
 playbooks/proposal/propose_update.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/playbooks/proposal/propose_update.sh b/playbooks/proposal/propose_update.sh
index 038d03d7ba..f264f8fe9a 100755
--- a/playbooks/proposal/propose_update.sh
+++ b/playbooks/proposal/propose_update.sh
@@ -34,7 +34,7 @@ elif [ "$OWN_PROJECT" == "requirements-constraints" ] ; then
     PROJECTS=openstack/requirements
     VENV=$(mktemp -d)
     trap "rm -rf $VENV" EXIT
-    virtualenv $VENV
+    virtualenv -p python3 $VENV
     $VENV/bin/pip install -e .
     function update {
         $VENV/bin/generate-constraints -b blacklist.txt -p /usr/bin/python3.6 \