stackforge/pecan
Code Issues Proposed changes

Address review comments

Browse Source 
A few typos and other changes based on the comments
from reviewing the previous changeset.

Change-Id: I0457db3496997586ad8e0432eea3eeda1641fae8
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
This commit is contained in:
Doug Hellmann
2013-05-06 11:25:32 -04:00
parent ee74648851
commit 649af77ec0
4 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/source/quick_start.rst
View File

@@ -113,7 +113,7 @@ Running the Application
The base project template creates the configuration file with the The base project template creates the configuration file with the
basic settings you need to run your Pecan application in basic settings you need to run your Pecan application in
``config.py``. This file includes the host and port to run the serves ``config.py``. This file includes the host and port to run the server
on, the location where your controllers and templates are stored on on, the location where your controllers and templates are stored on
disk, and the name of the directory containing any static files. disk, and the name of the directory containing any static files.

2
docs/source/routing.rst
View File

@@ -193,7 +193,7 @@ The :func:`_lookup` special method provides a way to process a portion of a URL,
and then return a new controller object to route to for the remainder. and then return a new controller object to route to for the remainder.
A :func:`_lookup` method may accept one or more arguments, segments A :func:`_lookup` method may accept one or more arguments, segments
chunks of the URL path to be processed (split on of the URL path to be processed (split on
``/``). :func:`_lookup` should also take variable positional arguments ``/``). :func:`_lookup` should also take variable positional arguments
representing the rest of the path, and it should include any portion representing the rest of the path, and it should include any portion
of the path it does not process in its return value. The example below of the path it does not process in its return value. The example below

2
docs/source/secure_controller.rst
View File

@@ -61,7 +61,7 @@ To secure a class, invoke with two arguments::
unclassified = UnclassifiedController() unclassified = UnclassifiedController()
``SecureControler`` ``SecureController``
------------------- -------------------
Alternatively, the same functionality can also be accomplished by Alternatively, the same functionality can also be accomplished by

4
docs/source/testing.rst
View File

@@ -6,7 +6,7 @@ Tests can live anywhere in your Pecan project as long as the test runner can
discover them. Traditionally, they exist in a package named ``myapp.tests``. discover them. Traditionally, they exist in a package named ``myapp.tests``.
The suggested mechanism for unit and integration testing of a Pecan application The suggested mechanism for unit and integration testing of a Pecan application
is the ``unittest`` module. is the :mod:`unittest` module.
Test Discovery and Other Tools Test Discovery and Other Tools
------------------------------ ------------------------------
@@ -120,7 +120,7 @@ A functional test for this controller might look something like
In addition to :attr:`webtest.TestResponse.body`, Pecan also provides In addition to :attr:`webtest.TestResponse.body`, Pecan also provides
:attr:`webtest.TestResponse.namespace`, which represents the template namespace :attr:`webtest.TestResponse.namespace`, which represents the template namespace
returned from the controller, and :attr:`webtest.TestResponse.template_name`, which returned from the controller, and :attr:`webtest.TestResponse.template_name`, which
yields the name of the template used. contains the name of the template used.
:: ::