Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/tools/setup/setup_venvs.py

28 lines
933 B
Python
Raw Normal View History

py3: Switch almost all shebang lines to use `python3`. This causes `upgrade-zulip-from-git`, as well as a no-option run of `tools/build-release-tarball`, to produce a Zulip install running Python 3, rather than Python 2. In particular this means that the virtualenv we create, in which all application code runs, is Python 3. One shebang line, on `zulip-ec2-configure-interfaces`, explicitly keeps Python 2, and at least one external ops script, `wal-e`, also still runs on Python 2. See discussion on the respective previous commits that made those explicit. There may also be some other third-party scripts we use, outside of this source tree and running outside our virtualenv, that still run on Python 2.
2017-08-02 23:15:16 +02:00
#!/usr/bin/env python3
Factor out venv-installing code into a module. Factor out the code in tools/provision.py which installs a python2 and python3 venv into a module (tools/setup/setup_venvs.py) which can also be used as a script.
2016-07-21 01:56:50 +02:00
import os
import sys
python: Add lint rule banning 'from os.path import'. This enforces our use of a consistent style in how we access Python modules; "from os.path import dirname" is a particularly popular abbreviation inconsistent with our style, and so it deserves a lint rule. Commit message and error text tweaked by tabbott. Fixes #6543.
2017-09-22 08:15:01 +02:00
ZULIP_PATH = os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
Factor out venv-installing code into a module. Factor out the code in tools/provision.py which installs a python2 and python3 venv into a module (tools/setup/setup_venvs.py) which can also be used as a script.
2016-07-21 01:56:50 +02:00
if ZULIP_PATH not in sys.path:
sys.path.append(ZULIP_PATH)
from scripts.lib.setup_venv import setup_virtualenv
setup_venvs: Use system python3. Otherwise python3 will be perpetually copied from virtualenv to virtualenv and will never receive updates from the system. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-24 01:07:28 +02:00
from scripts.lib.zulip_tools import overwrite_symlink
Factor out venv-installing code into a module. Factor out the code in tools/provision.py which installs a python2 and python3 venv into a module (tools/setup/setup_venvs.py) which can also be used as a script.
2016-07-21 01:56:50 +02:00
py3: Cut Python 2 codepaths from provision.
2017-08-09 00:38:30 +02:00
VENV_PATH = "/srv/zulip-py3-venv"
Ensure virtualenv is run throughout the entire Travis dev provision.
2017-06-17 15:14:59 +02:00
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
DEV_REQS_FILE = os.path.join(ZULIP_PATH, "requirements", "dev.txt")
requirements: Compile thumbor requirements with pip-tools on Python 2. The reason that `pip-tools` running on Python 3 didn’t detect the right requirements for `thumbor` on Python 2 is simply that some of them are conditional on the Python version. As for the requirements that had been manually added as a workaround: `backports-abc` and `singledispatch` are now correctly detected, while `backports.ssl-match-hostname` was vendored into `urllib3` some time ago and `certifi` is no longer necessary. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-09-23 00:42:40 +02:00
THUMBOR_REQS_FILE = os.path.join(ZULIP_PATH, "requirements", "thumbor-dev.txt")
Ensure virtualenv is run throughout the entire Travis dev provision.
2017-06-17 15:14:59 +02:00
provision: Remove transitional Python 2->3 logic in setup_venvs. At this point if we were accidentally using `/srv/zulip-venv` for anything, we'd have run into it by now. So just drop the bit of historical logic that we had to ensure that.
2017-12-19 06:49:51 +01:00
def main() -> None:
thumbor: Add thumbor on port 9995 in development. For now, this does nothing in a production environment, but it should simplify the process of doing testing on the Thumbor implementation, by integrating a lot of dependency management logic.
2017-11-09 16:31:57 +01:00
setup_virtualenv("/srv/zulip-thumbor-venv", THUMBOR_REQS_FILE,
setup_venvs.py: Enforce Python 2.7 for zulip-thumbor-venv setup. zulip-thumbor-venv runs only with Python 2.7. This could cause provision failures on setups where Python 2.7 is not the default.
2018-01-31 11:00:16 +01:00
patch_activate_script=True, virtualenv_args=['-p', 'python2.7'])
tools: Create DEPLOY_ROOT/zulip-py3-venv symlink in development too. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2019-02-07 02:14:01 +01:00
cached_venv_path = setup_virtualenv(
VENV_PATH, DEV_REQS_FILE, patch_activate_script=True,
setup_venvs: Use system python3. Otherwise python3 will be perpetually copied from virtualenv to virtualenv and will never receive updates from the system. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-24 01:07:28 +02:00
virtualenv_args=['-p', 'python3'])
tools: Create DEPLOY_ROOT/zulip-py3-venv symlink in development too. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2019-02-07 02:14:01 +01:00
overwrite_symlink(cached_venv_path, os.path.join(ZULIP_PATH, "zulip-py3-venv"))
Factor out venv-installing code into a module. Factor out the code in tools/provision.py which installs a python2 and python3 venv into a module (tools/setup/setup_venvs.py) which can also be used as a script.
2016-07-21 01:56:50 +02:00
if __name__ == "__main__":
main()