Specify python2 and clarify coverage requirements
diff --git a/bootstrap/dev/venv.sh b/bootstrap/dev/venv.sh
index 90088ac9bb7..d6cf95bb59c 100755
--- a/bootstrap/dev/venv.sh
+++ b/bootstrap/dev/venv.sh
@@ -1,6 +1,8 @@
 #!/bin/sh -xe
 # Developer virtualenv setup for Let's Encrypt client
 
+export VENV_ARGS="--python python2"
+
 ./bootstrap/dev/_venv_common.sh \
   -r requirements.txt \
   -e acme[testing] \
diff --git a/docs/contributing.rst b/docs/contributing.rst
index 3959ccee10e..3277d321a7b 100644
--- a/docs/contributing.rst
+++ b/docs/contributing.rst
@@ -7,9 +7,9 @@ Contributing
 Hacking
 =======
 
-The code base, including your pull requests, **must** have 100% unit
-test coverage, pass our `integration`_ tests **and** be compliant with
-the :ref:`coding style <coding-style>`.
+All changes in your pull request **must** have 100% unit test coverage, pass
+our `integration`_ tests, **and** be compliant with the
+:ref:`coding style <coding-style>`.
 
 
 Bootstrap

Please take a look at this @kuba. Not sure how I missed this yesterday. `venv.sh` needs to specify `python2` (Arch problems) and we can't require contributors to have 100% unit test coverage of the code base as that's not something we currently have.
