zulip

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
Tim Abbott	40aa8a2336	clean-venv-cache: Fix python 3 compatibility.	2016-06-27 20:39:22 -07:00
Tim Abbott	404c61ba97	clean-venv-cache: Use better approach to pruning caches. Rather than looking at which venvs are used by this particular build, we instead look at which venvs have a hash that is the hash_reqs value of a current requirements.txt file.	2016-06-27 20:30:39 -07:00
Tim Abbott	7d5c1864f7	clean-venv-cache: Avoid cleaning production venvs.	2016-06-27 20:08:45 -07:00
Eklavya Sharma	149938d468	Change shebangs from python2.7 to python.	2016-05-29 05:03:08 -07:00
Tim Abbott	dd40f51fee	Add code to clean the venv cache of old venvs.	2016-05-03 15:04:03 -07:00