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
|
2018-11-29 22:22:01 +01:00
|
|
|
from __future__ import (print_function)
|
2012-08-28 18:45:35 +02:00
|
|
|
import os
|
|
|
|
import sys
|
2018-12-01 17:23:17 +01:00
|
|
|
import configparser
|
2018-11-29 22:22:01 +01:00
|
|
|
if sys.version_info <= (3, 0):
|
|
|
|
print("Error: Zulip is a Python 3 project, and cannot be run with Python 2.")
|
|
|
|
print("Use e.g. `/path/to/manage.py` not `python /path/to/manage.py`.")
|
|
|
|
sys.exit(1)
|
2012-08-28 18:45:35 +02:00
|
|
|
|
2016-06-25 17:07:13 +02:00
|
|
|
BASE_DIR = os.path.dirname(os.path.abspath(__file__))
|
|
|
|
sys.path.append(BASE_DIR)
|
2020-01-08 00:06:39 +01:00
|
|
|
from scripts.lib.setup_path import setup_path
|
|
|
|
|
|
|
|
setup_path()
|
|
|
|
|
2018-11-19 19:50:25 +01:00
|
|
|
from scripts.lib.zulip_tools import assert_not_running_as_root
|
2016-06-25 17:07:13 +02:00
|
|
|
|
2012-08-28 18:45:35 +02:00
|
|
|
if __name__ == "__main__":
|
2018-11-19 19:50:25 +01:00
|
|
|
assert_not_running_as_root()
|
2018-12-01 17:23:17 +01:00
|
|
|
|
|
|
|
config_file = configparser.RawConfigParser()
|
|
|
|
config_file.read("/etc/zulip/zulip.conf")
|
|
|
|
PRODUCTION = config_file.has_option('machine', 'deploy_type')
|
|
|
|
HAS_SECRETS = os.access('/etc/zulip/zulip-secrets.conf', os.R_OK)
|
|
|
|
|
|
|
|
if PRODUCTION and not HAS_SECRETS:
|
2018-07-30 21:09:24 +02:00
|
|
|
# The best way to detect running manage.py as another user in
|
|
|
|
# production before importing anything that would require that
|
|
|
|
# access is to check for access to /etc/zulip/zulip.conf (in
|
|
|
|
# which case it's a production server, not a dev environment)
|
|
|
|
# and lack of access for /etc/zulip/zulip-secrets.conf (which
|
|
|
|
# should be only readable by root and zulip)
|
|
|
|
print("Error accessing Zulip secrets; manage.py in production must be run as the zulip user.")
|
|
|
|
sys.exit(1)
|
|
|
|
|
2013-11-19 00:04:45 +01:00
|
|
|
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "zproject.settings")
|
|
|
|
from django.conf import settings
|
2017-08-18 22:23:46 +02:00
|
|
|
from django.core.management import execute_from_command_line
|
2017-07-07 20:50:50 +02:00
|
|
|
from django.core.management.base import CommandError
|
2017-08-18 06:36:37 +02:00
|
|
|
from scripts.lib.zulip_tools import log_management_command
|
2013-11-19 00:04:45 +01:00
|
|
|
|
2017-08-18 06:36:37 +02:00
|
|
|
log_management_command(" ".join(sys.argv), settings.MANAGEMENT_LOG_PATH)
|
2013-05-22 21:18:45 +02:00
|
|
|
|
2017-08-18 22:23:46 +02:00
|
|
|
os.environ.setdefault("PYTHONSTARTUP", os.path.join(BASE_DIR, "scripts/lib/pythonrc.py"))
|
2013-05-22 21:18:45 +02:00
|
|
|
if "--no-traceback" not in sys.argv and len(sys.argv) > 1:
|
|
|
|
sys.argv.append("--traceback")
|
2017-07-07 20:50:50 +02:00
|
|
|
try:
|
|
|
|
execute_from_command_line(sys.argv)
|
|
|
|
except CommandError as e:
|
|
|
|
print(e, file=sys.stderr)
|
|
|
|
sys.exit(1)
|