mirror of https://github.com/zulip/zulip.git
c039f73656
Travis enables different Python versions through virtual environments, but it seems that there is a little caveat when we try to create Zulip's virtual environment by referring Travis' virtual environment; Zulip's virtual environment refers the system Python. We encountered this behaviour when we tried to run our backend test suite under Python 3.5 in Travis. 'python3 --version' command before activating Zulip's virtualenv showed 'Python 3.5.3' and after it showed 'Python 3.4.3'. This happened when we created the virtual environment using 'virtualenv -p python3'. The solution seems to be to explicitly give the path of the Python interpreter in the Travis' virtual environment using 'which python3'. |
||
|---|---|---|
| .. | ||
| emoji | ||
| __init__.py | ||
| build_pygments_data.py | ||
| generate-fixtures | ||
| generate-test-credentials | ||
| install-aws-server | ||
| lang.json | ||
| postgres-init-dev-db | ||
| postgres-init-test-db | ||
| setup_venvs.py | ||