summaryrefslogtreecommitdiff
path: root/docs/narr
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2013-10-07 19:47:32 -0700
committerSteve Piercy <web@stevepiercy.com>2013-10-07 19:47:32 -0700
commite893a0ecc0bc9929fcda1103b510991954dbdc6e (patch)
tree526cc6ca9bd61a99bc845c19b24e92e25cb9802f /docs/narr
parent13cf2dd2c912c1961d429c8a5756622cf960d5bf (diff)
parenta26d09f291bdf4f9c7853b1dbfc9643a678a7b94 (diff)
downloadpyramid-e893a0ecc0bc9929fcda1103b510991954dbdc6e.tar.gz
pyramid-e893a0ecc0bc9929fcda1103b510991954dbdc6e.tar.bz2
pyramid-e893a0ecc0bc9929fcda1103b510991954dbdc6e.zip
Merge branch 'doc_render_to_response2' of github.com:kpinc/pyramid into kpinc-doc_render_to_response2
Diffstat (limited to 'docs/narr')
-rw-r--r--docs/narr/introduction.rst11
-rw-r--r--docs/narr/renderers.rst10
2 files changed, 15 insertions, 6 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index 032f4be6b..8c2acf95c 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -321,7 +321,14 @@ assertion instead that the view returns "the right stuff" in the dictionary
it returns. You can write "real" unit tests instead of functionally testing
all of your views.
-For example, instead of:
+.. index::
+ pair: renderer; explicitly calling
+ pair: view renderer; explictly calling
+
+.. _example_render_to_response_call:
+
+For example, instead of returning a ``Response`` object from a
+``render_to_response`` call:
.. code-block:: python
:linenos:
@@ -332,7 +339,7 @@ For example, instead of:
return render_to_response('myapp:templates/mytemplate.pt', {'a':1},
request=request)
-You can do this:
+You can return a Python dictionary:
.. code-block:: python
:linenos:
diff --git a/docs/narr/renderers.rst b/docs/narr/renderers.rst
index 4046c67fa..740c81555 100644
--- a/docs/narr/renderers.rst
+++ b/docs/narr/renderers.rst
@@ -56,10 +56,12 @@ serialization techniques. In practice, renderers obtain application data
values from Python dictionaries so, in practice, view callables which use
renderers return Python dictionaries.
-View configuration can vary the renderer associated with a view callable via
-the ``renderer`` attribute. For example, this call to
-:meth:`~pyramid.config.Configurator.add_view` associates the ``json`` renderer
-with a view callable:
+View callables can :ref:`explicitly call <example_render_to_response_call>`
+renderers, but typically don't. Instead view configuration declares the
+renderer used to render a view callable's results. This is done with the
+``renderer`` attribute. For example, this call to
+:meth:`~pyramid.config.Configurator.add_view` associates the ``json``
+renderer with a view callable:
.. code-block:: python