mitmproxy/dev.sh

#!/bin/sh
set -e
set -x

PYVERSION=$1
VENV="venv$1"

echo "Creating dev environment in $VENV using Python $PYVERSION"

python$PYVERSION -m virtualenv "$VENV" --always-copy
. "$VENV/bin/activate"
pip$PYVERSION install -q -U pip setuptools
pip$PYVERSION install -q -r requirements.txt

echo ""
echo "* Virtualenv created in $VENV and all dependencies installed."
echo "* You can now activate the $(python --version) virtualenv with this command: \`. $VENV/bin/activate\`"
add a py3 venv in dev environment This allows us to run e.g. tests in a different python version: $ venv3/bin/py.test test/netlib/test_tcp.py 2016-05-25 17:42:22 +00:00			`#!/bin/sh`
merged with upstream changes in dev 2015-06-24 01:50:51 +00:00			`set -e`
Better debugging output. 2016-06-03 01:42:15 +00:00			`set -x`
add a py3 venv in dev environment This allows us to run e.g. tests in a different python version: $ venv3/bin/py.test test/netlib/test_tcp.py 2016-05-25 17:42:22 +00:00
Refactor dev.sh - Parameterise the Python version. All of these now work: ./dev.sh # Use default Python version ./dev.sh 2.7 # Explicitly use 2.7 in venv2.7 ./dev.sh 3.5 # Explicitly use 3.5 in venv3.5 This should also work for Travis, which has a weird setup where Pytho3 can be 3.4. 2016-05-25 21:35:21 +00:00			`PYVERSION=$1`
			`VENV="venv$1"`
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
Refactor dev.sh - Parameterise the Python version. All of these now work: ./dev.sh # Use default Python version ./dev.sh 2.7 # Explicitly use 2.7 in venv2.7 ./dev.sh 3.5 # Explicitly use 3.5 in venv3.5 This should also work for Travis, which has a weird setup where Pytho3 can be 3.4. 2016-05-25 21:35:21 +00:00			`echo "Creating dev environment in $VENV using Python $PYVERSION"`

			`python$PYVERSION -m virtualenv "$VENV" --always-copy`
			`. "$VENV/bin/activate"`
			`pip$PYVERSION install -q -U pip setuptools`
			`pip$PYVERSION install -q -r requirements.txt`
./dev: echo what we have done 2015-03-14 02:08:34 +00:00
			`echo ""`
add a py3 venv in dev environment This allows us to run e.g. tests in a different python version: $ venv3/bin/py.test test/netlib/test_tcp.py 2016-05-25 17:42:22 +00:00			`echo "* Virtualenv created in $VENV and all dependencies installed."`
			echo "* You can now activate the $(python --version) virtualenv with this command: \`. $VENV/bin/activate\`"