summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-22 22:43:55 +0300
committerTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-22 22:43:55 +0300
commit6ce39f11b76dc599dfc897eab43bcf236b26c5d5 (patch)
treec6f2d81b7b6d08fed1008a1acff75554eaf49b1d /docs
parentf082bbd16610b6454c475bb77d0269a690fc3ac1 (diff)
downloadpyramid-6ce39f11b76dc599dfc897eab43bcf236b26c5d5.tar.gz
pyramid-6ce39f11b76dc599dfc897eab43bcf236b26c5d5.tar.bz2
pyramid-6ce39f11b76dc599dfc897eab43bcf236b26c5d5.zip
remove redundant text
Also, this fact has already been explained in the chapter, so mention that.
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/renderers.rst10
1 files changed, 4 insertions, 6 deletions
diff --git a/docs/narr/renderers.rst b/docs/narr/renderers.rst
index b4eb95186..bcab0e3f4 100644
--- a/docs/narr/renderers.rst
+++ b/docs/narr/renderers.rst
@@ -80,12 +80,10 @@ response attributes (such as headers and the HTTP status code) by attaching a
property to the ``request.response`` attribute.
See :ref:`request_response_attr`.
-If the :term:`view callable` associated with a :term:`view configuration`
-returns a Response object directly, any renderer associated with the view
-configuration is ignored, and the response is passed back to :app:`Pyramid`
-unchanged. For example, if your view callable returns an instance of the
-:class:`pyramid.response.Response` class as a response, no renderer
-will be employed.
+As already mentioned, if the :term:`view callable` associated with a
+:term:`view configuration` returns a Response object (or its instance),
+any renderer associated with the view configuration is ignored,
+and the response is passed back to :app:`Pyramid` unchanged. For example:
.. code-block:: python
:linenos: