From b15a06346148f6095adf17893490175abc95a494 Mon Sep 17 00:00:00 2001
From: Steve Piercy <web@stevepiercy.com>
Date: Tue, 09 Oct 2018 09:14:00 +0200
Subject: [PATCH] Rearrange introduction of Setuptools and move to debugtoolbar. Replace [testing] with [dev]. Make narrative text more descriptive of what is going on with `extras_require`

---
 docs/quick_tutorial/unit_testing.rst |    7 +------
 1 files changed, 1 insertions(+), 6 deletions(-)

diff --git a/docs/quick_tutorial/unit_testing.rst b/docs/quick_tutorial/unit_testing.rst
index dc14a19..6549253 100644
--- a/docs/quick_tutorial/unit_testing.rst
+++ b/docs/quick_tutorial/unit_testing.rst
@@ -57,7 +57,7 @@
         :emphasize-lines: 15
 
 #.  Install our project and its newly added dependency.
-    Note that we use the extra specifier ``[dev]`` to install testing requirements and surround it with double quote marks.
+    Note that we use the extra specifier ``[dev]`` to install testing requirements for development and surround it and the period with double quote marks.
 
     .. code-block:: bash
 
@@ -101,11 +101,6 @@
 ``pyramid.testing.tearDown()`` aren't actually necessary here; they are only
 necessary when your test needs to make use of the ``config`` object (it's a
 Configurator) to add stuff to the configuration state before calling the view.
-
-Finally we've introduced the concept of :term:`Setuptools` extras.
-These are optional or recommended features that may be installed with an "extras" specifier.
-The specifier is the name of a key in a Python dictionary, and is surrounded by square brackets when invoked on the command line.
-The value for the key is a Python list of dependencies.
 
 
 Extra credit

--
Gitblit v1.9.3