mirror of https://github.com/zulip/zulip.git
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. |
||
|---|---|---|
| .. | ||
| configure-rabbitmq | ||
| flush-memcached | ||
| generate-self-signed-certs | ||
| generate_secrets.py | ||
| initialize-database | ||
| install | ||
| node-wrapper | ||
| pgroonga-debian.asc | ||
| pgroonga-ppa.asc | ||
| postgres-init-db | ||
| terminate-psql-sessions | ||
| zulip-ppa.asc | ||