Files
zulip/tools/update-locked-requirements
Greg Price d3a69da829 py3: Fix or remove (almost) all references to Python 2 venv in docs.
I think soon we'll put the Python 3 venv at `/srv/zulip-venv` and
make `/srv/zulip-py3-venv` just an alias to that (then remove the
alias too), but for now the old name is helpful for spotting places
that need an update.

The `/srv/zulip-venv` name still appears in codepaths used by Travis
tests.
2017-08-08 15:48:12 -07:00

20 lines
720 B
Bash
Executable File

#!/usr/bin/env bash
set -e
# Check if zulip-.*venv in particular has been installed
# It is sufficient to check just for /srv/zulip-py3-venv because it must be
# present in both cases of py2 and py3
if [ ! -d /srv/zulip-py3-venv ]; then
./tools/setup/setup_venvs.py
fi
source /srv/zulip-py3-venv/bin/activate # Activate python3 virtualenv
pip-compile --output-file requirements/py3_common_lock.txt requirements/py3_common.txt
# Remove the editable flag in the lock file for safer build
sed -i 's/-e //' requirements/py3_common_lock.txt
# pip-tools bug; future, futures are obsolete in python3
sed -i '/futures==/d' requirements/py3_common_lock.txt
sed -i '/future==/d' requirements/py3_common_lock.txt
deactivate