From cb000eb749af452f7a1dbc13ce7f33816d346376 Mon Sep 17 00:00:00 2001 From: Nils Dijk Date: Wed, 27 Oct 2021 14:56:57 +0200 Subject: [PATCH] update readme with simplified pipenv commands --- src/test/regress/mitmscripts/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/test/regress/mitmscripts/README.md b/src/test/regress/mitmscripts/README.md index 15d6797f6..6d8d928a7 100644 --- a/src/test/regress/mitmscripts/README.md +++ b/src/test/regress/mitmscripts/README.md @@ -17,7 +17,7 @@ Automated Failure Testing works by inserting a network proxy (mitmproxy) between ## Getting Started -First off, to use this you'll need mitmproxy, I recommend version `3.0.4`, and I also recommend running it with `python 3.6`. This script integrates pretty deeply with mitmproxy so other versions might fail to work. +First off, to use this you'll need mitmproxy, I recommend version `7.0.4`, and I also recommend running it with `python 3.9`. This script integrates pretty deeply with mitmproxy so other versions might fail to work. I highly recommend using pipenv to install mitmproxy. It lets you easily manage isolated environments (instead of installing python packages globally). If you've heard of virtualenv, pipenv is that but much easier to use. @@ -25,7 +25,7 @@ Once you've installed it: ```bash $ cd src/test/regress -$ pipenv --python 3.6 --python=`which python3.6` +$ pipenv --rm # removes any previous available pipenv $ pipenv install # there's already a Pipfile.lock in src/test/regress with packages $ pipenv shell # this enters the virtual environment, putting mitmproxy onto $PATH ```