zulip

Commit Graph

Author	SHA1	Message	Date
Greg Price	a099e698e2	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-16 17:54:43 -07:00
Taranjeet Singh	d606b95242	zulip_tools.py: Move zulip_tools.py in scripts/lib. This commit moves zulip_tools.py as part of cleaning the root directory and organizing proejct into better directory structure.	2016-08-15 16:44:50 -07:00
Tim Abbott	91b1521578	purge-old-deployments: Avoid purging last/next deployments.	2016-08-04 17:02:48 -07:00
Eklavya Sharma	149938d468	Change shebangs from python2.7 to python.	2016-05-29 05:03:08 -07:00
Steven Oud	d5435fad1d	Consistently use /usr/bin/env python2.7 in shebangs and commands.	2015-10-21 22:58:21 +00:00
Tim Abbott	bc19be977a	purge-old-deployments: Never purge the currently running deployment. (imported from commit edccfc908f50a66e5c214bca8a5418625ed64bf0)	2013-11-04 13:22:41 -05:00
Tim Abbott	adc5771062	Rename purge-deployments to purge-old-deployments. Since this is a user-facing script, we should make it more clear about what it does. (imported from commit eecaed8462a92fe7c688df5c32fea2e088b25058)	2013-11-04 13:22:41 -05:00

7 Commits