summaryrefslogtreecommitdiff
path: root/docs/narr/hooks.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/narr/hooks.rst')
-rw-r--r--docs/narr/hooks.rst10
1 files changed, 7 insertions, 3 deletions
diff --git a/docs/narr/hooks.rst b/docs/narr/hooks.rst
index 0dcbcd371..df081d35c 100644
--- a/docs/narr/hooks.rst
+++ b/docs/narr/hooks.rst
@@ -218,7 +218,7 @@ Another (deprecated) mechanism which allows event subscribers more control
when adding renderer global values exists in :ref:`adding_renderer_globals`.
.. index::
- single: renderer globals
+ single: adding renderer globals
.. _adding_renderer_globals:
@@ -284,8 +284,8 @@ Using Response Callbacks
Unlike many other web frameworks, :app:`Pyramid` does not eagerly create a
global response object. Adding a :term:`response callback` allows an
-application to register an action to be performed against a response object
-once it is created, usually in order to mutate it.
+application to register an action to be performed against whatever response
+object is returned by a view, usually in order to mutate the response.
The :meth:`pyramid.request.Request.add_response_callback` method is used to
register a response callback.
@@ -528,6 +528,7 @@ The default context URL generator is available for perusal as the class
.. index::
single: IResponse
+ single: special view responses
.. _using_iresponse:
@@ -615,6 +616,9 @@ to make sure the object implements every attribute and method outlined in
:class:`pyramid.interfaces.IResponse` and you'll have to ensure that it's
marked up with ``zope.interface.implements(IResponse)``:
+.. code-block:: python
+ :linenos:
+
from pyramid.interfaces import IResponse
from zope.interface import implements