mitmproxy/dev.sh

#!/bin/bash
set -e
VENV=./venv

python -m virtualenv $VENV --always-copy
. $VENV/bin/activate
pip install -e ./netlib[dev]
pip install -e ./pathod[dev]
pip install -e ./mitmproxy[dev,examples,contentviews]

echo ""
echo "* Created virtualenv environment in $VENV."
echo "* Installed all dependencies into the virtualenv."
echo "* You can now activate the virtualenv: \`. $VENV/bin/activate\`"
merged with upstream changes in dev 2015-06-24 01:50:51 +00:00			`#!/bin/bash`
			`set -e`
merge metadata files 2016-02-15 14:43:59 +00:00			`VENV=./venv`
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
fix #778 2015-09-19 09:18:57 +00:00			`python -m virtualenv $VENV --always-copy`
fix virtualenv activation 2015-08-19 13:10:15 +00:00			`. $VENV/bin/activate`
merge metadata files 2016-02-15 14:43:59 +00:00			`pip install -e ./netlib[dev]`
			`pip install -e ./pathod[dev]`
			`pip install -e ./mitmproxy[dev,examples,contentviews]`
./dev: echo what we have done 2015-03-14 02:08:34 +00:00
			`echo ""`
			`echo "* Created virtualenv environment in $VENV."`
			`echo "* Installed all dependencies into the virtualenv."`
fix #778 2015-09-19 09:18:57 +00:00			echo "* You can now activate the virtualenv: \`. $VENV/bin/activate\`"