From f853d5592ec7f901a50381de22a26a9ab098f885 Mon Sep 17 00:00:00 2001
From: Jaap Roes <jaap.roes@gmail.com>
Date: Fri, 3 May 2019 20:18:42 +0200
Subject: [PATCH] "python3 -m pip" is clearer (thanks @jaap3) (#368)

---
 docs/contributing.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/contributing.rst b/docs/contributing.rst
index cdea6def..0f4d63dd 100644
--- a/docs/contributing.rst
+++ b/docs/contributing.rst
@@ -33,12 +33,12 @@ If you just want to get started without creating your own fork, you can do this
 The next step is to create a virtual environment for your project and use it to install Datasette's dependencies::
 
     cd datasette
-    # Create a virtual environment in venv/
-    python3 -mvenv venv
+    # Create a virtual environment in ./venv
+    python3 -m venv ./venv
     # Now activate the virtual environment, so pip can install into it
     source venv/bin/activate
     # Install Datasette and its testing dependencies
-    pip install -e .[test]
+    python3 -m pip -e .[test]
 
 That last line does most of the work: ``pip install -e`` means "install this package in a way that allows me to edit the source code in place". The ``.[test]`` option means "use the setup.py in this directory and install the optional testing dependencies as well".