Browse code
Create virtualenv with abstracted VIRTUALENV_CMD
Just calling "virtualenv" makes a Python 2 based environment;
setuptools just dropped Python 2 support (as Python 2 reached EOL in
Jan 2020) so this has now become a breakage.
Although the Python 2 path won't work, use the abstracted command.
This should stop us having to revisit this for any future cleanups (or
switing to venv, etc).
Change-Id: I531e971b78491a9276753c0d86b04c4adbd224aa
Ian Wienand authored on 2020/01/13 14:05:11Showing 1 changed files
| ... | ... |
@@ -29,7 +29,7 @@ GITDIR["pbr"]=$DEST/pbr |
| 29 | 29 |
# install_infra() - Collect source and prepare |
| 30 | 30 |
function install_infra {
|
| 31 | 31 |
local PIP_VIRTUAL_ENV="$REQUIREMENTS_DIR/.venv" |
| 32 |
- [ ! -d $PIP_VIRTUAL_ENV ] && virtualenv $PIP_VIRTUAL_ENV |
|
| 32 |
+ [ ! -d $PIP_VIRTUAL_ENV ] && ${VIRTUALENV_CMD} $PIP_VIRTUAL_ENV
|
|
| 33 | 33 |
# We don't care about testing git pbr in the requirements venv. |
| 34 | 34 |
PIP_VIRTUAL_ENV=$PIP_VIRTUAL_ENV pip_install -U pbr |
| 35 | 35 |
PIP_VIRTUAL_ENV=$PIP_VIRTUAL_ENV pip_install $REQUIREMENTS_DIR |