mirror of
https://github.com/zulip/zulip.git
synced 2025-11-03 13:33:24 +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.
21 lines
672 B
Python
21 lines
672 B
Python
#!/usr/bin/env python3
|
|
from __future__ import print_function
|
|
|
|
import os
|
|
import pwd
|
|
import sys
|
|
|
|
def check_venv(filename):
|
|
# type: (str) -> None
|
|
try:
|
|
import ujson
|
|
except ImportError:
|
|
print("You need to run %s inside a Zulip dev environment." % (filename,))
|
|
user_id = os.getuid()
|
|
user_name = pwd.getpwuid(user_id).pw_name
|
|
if user_name != 'vagrant' and user_name != 'zulipdev':
|
|
print("If you are using Vagrant, you can `vagrant ssh` to enter the Vagrant guest.")
|
|
else:
|
|
print("You can `source /srv/zulip-py3-venv/bin/activate` to enter the Zulip development environment.")
|
|
sys.exit(1)
|