summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rwxr-xr-xdocs/convert_images.sh2
-rw-r--r--docs/narr/configuration.rst9
-rw-r--r--docs/narr/contextfinding.rst13
-rw-r--r--docs/narr/firstapp.rst10
-rw-r--r--docs/narr/install.rst1
-rw-r--r--docs/narr/introduction.rst2
-rw-r--r--docs/narr/project.rst13
-rw-r--r--docs/narr/traversal.rst2
8 files changed, 30 insertions, 22 deletions
diff --git a/docs/convert_images.sh b/docs/convert_images.sh
index 3bd22c01b..29539c6b5 100755
--- a/docs/convert_images.sh
+++ b/docs/convert_images.sh
@@ -1,4 +1,4 @@
-TEXDIR=.build/latex
+TEXDIR=_build/latex
if test ! -z $BOOK; then
for img in $TEXDIR/*.png;
diff --git a/docs/narr/configuration.rst b/docs/narr/configuration.rst
index ae02a5a6c..d55a190e2 100644
--- a/docs/narr/configuration.rst
+++ b/docs/narr/configuration.rst
@@ -10,9 +10,9 @@ Each deployment of an application written using :app:`Pyramid` implies a
specific *configuration* of the framework itself. For example, an
application which serves up MP3s for user consumption might plug code into
the framework that manages songs, while an application that manages corporate
-data might plug in code that manages accounting information. :app:`Pyramid`
-refers to the way in which code is plugged in to it for a specific
-application as "configuration".
+data might plug in code that manages accounting information. The way in which
+code is plugged in to :app:`Pyramid`, for a specific application, is referred
+to as "configuration".
Most people understand "configuration" as coarse settings that inform the
high-level operation of a specific application deployment. For instance,
@@ -21,8 +21,7 @@ application startup time as "configuration". :app:`Pyramid` extends this
pattern to application development, using the term "configuration" to express
standardized ways that code gets plugged into a deployment of the framework
itself. When you plug code into the :app:`Pyramid` framework, you are
-"configuring" :app:`Pyramid` for the purpose of creating a particular
-application deployment.
+"configuring" :app:`Pyramid` to create a particular application.
.. index::
single: imperative configuration
diff --git a/docs/narr/contextfinding.rst b/docs/narr/contextfinding.rst
index c3fbe7f5a..457e1a526 100644
--- a/docs/narr/contextfinding.rst
+++ b/docs/narr/contextfinding.rst
@@ -51,16 +51,15 @@ requesting user.
that do not provide a notion of a context.
There are two separate :term:`context finding` subsystems in
-:app:`Pyramid`: :term:`traversal` and :term:`URL dispatch`. The
-subsystems are documented within this chapter. They can be used
-separately or they can be combined. Three chapters which follow
-describe :term:`context finding`: :ref:`traversal_chapter`,
+:app:`Pyramid`: :term:`traversal` and :term:`URL dispatch`. They can
+be used separately or they can be combined. Three chapters which
+follow describe :term:`context finding`: :ref:`traversal_chapter`,
:ref:`urldispatch_chapter` and :ref:`hybrid_chapter`.
There is only one :term:`view lookup` subsystem present in
-:app:`Pyramid`. Where appropriate, within this chapter, we
-describe how view lookup interacts with context finding. One chapter
-which follows describes :term:`view lookup`: :ref:`views_chapter`.
+:app:`Pyramid`. Where appropriate, we will describe how view lookup
+interacts with context finding. One chapter which follows describes
+:term:`view lookup`: :ref:`views_chapter`.
Should I Use Traversal or URL Dispatch for Context Finding?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/docs/narr/firstapp.rst b/docs/narr/firstapp.rst
index 9d3cad13c..8835f395a 100644
--- a/docs/narr/firstapp.rst
+++ b/docs/narr/firstapp.rst
@@ -137,10 +137,10 @@ passed to the ``Response`` constructor as the *body* of the response. In the
Application Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~
-In the above script, the following code, representing the
-*configuration* of an application which uses the previously defined
-imports and function definitions is placed within the confines of an
-``if`` statement:
+In the above script, the following code represents the *configuration* of this
+simple application. The application is configured using the previously defined
+imports and function definitions, placed within the confines of an ``if``
+statement:
.. code-block:: python
:linenos:
@@ -242,7 +242,7 @@ circumstances which would cause the view configuration's callable to
be invoked. In general, a greater number of predicates supplied along
with a view configuration will more strictly limit the applicability
of its associated view callable. When :app:`Pyramid` processes a
-request, however, the view callable with the *most specific* view
+request, the view callable with the *most specific* view
configuration (the view configuration that matches the most specific
set of predicates) is always invoked.
diff --git a/docs/narr/install.rst b/docs/narr/install.rst
index c753b7298..5a8d7e459 100644
--- a/docs/narr/install.rst
+++ b/docs/narr/install.rst
@@ -86,7 +86,6 @@ the following commands:
[chrism@vitaminf ~]$ mkdir tmp
[chrism@vitaminf ~]$ mkdir opt
[chrism@vitaminf ~]$ cd tmp
- [chrism@vitaminf tmp]$ cd tmp
[chrism@vitaminf tmp]$ wget \
http://www.python.org/ftp/python/2.6.4/Python-2.6.4.tgz
[chrism@vitaminf tmp]$ tar xvzf Python-2.6.4.tgz
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index 725d32725..7c725690d 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -103,7 +103,7 @@ What Is The Pylons Project?
---------------------------
:app:`Pyramid` is a member of the collection of software published under the
-Pylons Project. :Pylons software is written by a loose-knit community of
+Pylons Project. Pylons software is written by a loose-knit community of
contributors. The `Pylons Project website <http://docs.pylonshq.com>`_
includes details about how :app:`Pyramid` relates to the Pylons Project.
diff --git a/docs/narr/project.rst b/docs/narr/project.rst
index 6e466b284..225ced59c 100644
--- a/docs/narr/project.rst
+++ b/docs/narr/project.rst
@@ -145,6 +145,17 @@ project we name ``MyProject``:
name during ``paster create`` by adding the project name to the
command line, e.g. ``paster create -t pyramid_starter MyProject``.
+.. note:: You may encounter an error when using ``paster create``
+ if a dependent Python package is not installed. This will
+ result in a traceback ending in:
+
+ .. code-block:: text
+
+ pkg_resources.DistributionNotFound: <package name>
+
+ Simply run ``bin/easy_install``, with the missing package
+ name from the error message, to workaround this issue.
+
As a result of invoking the ``paster create`` command, a project is
created in a directory named ``MyProject``. That directory is a
:term:`setuptools` :term:`project` directory from which a setuptools
@@ -752,7 +763,7 @@ also informs Python that the directory which contains it is a *package*.
:term:`context` of the request is an instance of the
:class:`myproject.models.MyModel` class. The first argument to
``add_view`` points at a Python function that does all the work for this
- view, also known as a :term:`view callable` via a :term:`dotted Python
+ view, also known as a :term:`view callable`, via a :term:`dotted Python
name`. The view declaration also names a ``renderer``, which in this case
is a template that will be used to render the result of the view callable.
This particular view declaration points at
diff --git a/docs/narr/traversal.rst b/docs/narr/traversal.rst
index 56594ed5a..67296d21a 100644
--- a/docs/narr/traversal.rst
+++ b/docs/narr/traversal.rst
@@ -360,7 +360,7 @@ and a :term:`view name`.
of path segments that come from ``PATH_INFO`` that are "left over"
after traversal has completed.
-Once :term:`context` and :term:`view name` and associated attributes
+Once :term:`context`, :term:`view name`, and associated attributes
such as the :term:`subpath` are located, the job of :term:`traversal`
is finished. It passes back the information it obtained to its
caller, the :app:`Pyramid` :term:`Router`, which subsequently