mirror of
https://github.com/zulip/zulip.git
synced 2025-11-04 14:03:30 +00:00
a099e698e2
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.
24 lines
739 B
Python
Executable File
24 lines
739 B
Python
Executable File
#!/usr/bin/env python3
|
|
|
|
# This script is only meant to be run from run-dev.py, which sets up the
|
|
# environment correctly and passes the correct arguments for manage.py. It is a
|
|
# separate script so that the import from zerver.worker.queue_processors (which
|
|
# is slow) can be done in parallel with the rest of the work in bringing up the
|
|
# dev server.
|
|
from __future__ import absolute_import
|
|
import sys
|
|
import os
|
|
import subprocess
|
|
|
|
# check for the venv
|
|
from lib import sanity_check
|
|
sanity_check.check_venv(__file__)
|
|
|
|
import django
|
|
sys.path.append(os.path.join(os.path.dirname(__file__), '..'))
|
|
django.setup()
|
|
|
|
args = sys.argv[1:]
|
|
subprocess.Popen(['./manage.py', 'process_queue', '--all'] + args,
|
|
stderr=subprocess.STDOUT)
|