summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2012-11-22 00:40:47 -0500
committerChris McDonough <chrism@plope.com>2012-11-22 00:40:47 -0500
commit5d9c28f4e7f1fd3eba75e5bb51aebcbb56440df8 (patch)
treea548c4c2314ab12e02caf11a16d8565faa79bd04 /docs
parent5acf4b4809e88dfeb3882f5033622a9517763d02 (diff)
downloadpyramid-5d9c28f4e7f1fd3eba75e5bb51aebcbb56440df8.tar.gz
pyramid-5d9c28f4e7f1fd3eba75e5bb51aebcbb56440df8.tar.bz2
pyramid-5d9c28f4e7f1fd3eba75e5bb51aebcbb56440df8.zip
more appeasement
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/install.rst11
1 files changed, 7 insertions, 4 deletions
diff --git a/docs/narr/install.rst b/docs/narr/install.rst
index 32f331550..663f0df6c 100644
--- a/docs/narr/install.rst
+++ b/docs/narr/install.rst
@@ -248,11 +248,14 @@ your setuptools-enabled Python interpreter, use the ``easy_install`` command.
Even though Python 3.3 and better comes with ``pyvenv`` out of the box,
which is similar to ``virtualenv``, we suggest using ``virtualenv`` instead.
``virtualenv`` works on well Python 3.3. This isn't a recommendation made
- for technical reasons, it's one made because it's not possible for the
+ for technical reasons, it's one made because it's not feasible for the
authors of this guide to explain setup using multiple virtual environment
- systems. ``pyenv`` will work fine. However, if you use ``pyvenv`` instead,
- you'll need to understand how to install software such as ``distribute``
- into the virtual environment manually, which this guide does not cover.
+ systems. We are aiming to not need to make the installation documentation
+ Turing-complete.
+
+ ``pyenv`` will work fine. However, if you use ``pyvenv`` instead, you'll
+ need to understand how to install software such as ``distribute`` into the
+ virtual environment manually, which this guide does not cover.
.. code-block:: text