Virtualenv is the one and only recommended dev environment

- Create a "dev" script to create a virtualenv-based dev environment
- Update the docs to remove non-virtualenv install recommendations
- Update osx-binaries generation to use virtualenv

TODO:
- The dev script or an equivalent should be made to work on Windows
- We still can't remove the annoying top-level command scripts, because
pyinstaller doesn't support entry points. Once it does, they can go.

1 files changed, 16 insertions, 0 deletions

diff --git a/dev b/dev
new file mode 100755
index 00000000..c8346af1
--- /dev/null
+++ b/dev
@@ -0,0 +1,16 @@
+#!/bin/sh
+VENV=../venv.mitmproxy
+PIP="$VENV/bin/pip --cache-dir ~/.pipcache"
+
+echo "This script sets up the following:"
+echo "\t~/.pipcache - A pip cache directory"
+echo "\t$VENV - A development virtualenv"
+
+mkdir -p ~/.pipcache
+
+virtualenv $VENV
+source $VENV/bin/activate
+$PIP install -r ./requirements.txt
+# Re-install these to make them editable
+$PIP install --editable ../netlib
+$PIP install --editable ../pathod