mitmproxy/dev

#!/bin/sh
VENV=../venv.mitmproxy

virtualenv $VENV
source $VENV/bin/activate
pip install --src .. -r requirements.txt
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. 2015-03-12 11:12:15 +00:00			`#!/bin/sh`
			`VENV=../venv.mitmproxy`

			`virtualenv $VENV`
			`source $VENV/bin/activate`
simplify virtualenv - add dev.bat for Windows users - remove ~/.pipcache creation. If that causes issues with PyInstaller, we should use pip --no-cache-dir there or rm -r pip.locations.USER_CACHE_DIR. - remove superfluous pip install calls. 2015-03-14 01:33:21 +00:00			`pip install --src .. -r requirements.txt`