zulip

Commit Graph

Author	SHA1	Message	Date
rht	7a96b8c7ad	tools/lib: Text-wrap long lines exceeding 110.	2017-11-10 16:24:09 -08:00
rht	9c5e0971f4	sanity_check: Check a few packages. This just makes our check for whether we're actually in a Zulip development environment better.	2017-10-17 22:21:33 -07:00
derAnfaenger	df948c7ea5	Remove useless shebang lines.	2017-10-11 12:52:36 -07:00
rht	f15bdce90e	tools: Remove print_function. Tweaked by tabbott to exclude the linter libraries.	2017-09-29 15:44:56 -07:00
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
Greg Price	d3a69da829	py3: Fix or remove (almost) all references to Python 2 venv in docs. I think soon we'll put the Python 3 venv at `/srv/zulip-venv` and make `/srv/zulip-py3-venv` just an alias to that (then remove the alias too), but for now the old name is helpful for spotting places that need an update. The `/srv/zulip-venv` name still appears in codepaths used by Travis tests.	2017-08-08 15:48:12 -07:00
sinwar	4296d608ab	test_server: Improve warning in venv check. This (1) changes test_server to use the common `check_venv` method and (2) improves check_venv to provide a clearer error message in the case that you're inside Vagrant but not in a venv. Tweaked by tabbott to borrow logic from run_dev.py.	2017-04-05 16:51:23 -07:00
sinwar	eab355b0cd	tools: Create more consistent checks for venv. This helps make the Zulip development environment somewhat more robust to new contributors, since it will give them a nice warning if they try running any of our development tools outside the Zulip virtualenv. Fixes #3468.	2017-02-06 21:50:32 -08:00

8 Commits