From 818768764a69198bd938cb268ea1c584a7007f52 Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Sun, 12 Dec 2010 11:05:00 -0700 Subject: simplify paragraph a bit --- docs/narr/templates.rst | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) (limited to 'docs') diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst index 028ef1a83..803758b82 100644 --- a/docs/narr/templates.rst +++ b/docs/narr/templates.rst @@ -117,14 +117,12 @@ In the examples above we pass in a keyword argument named ``request`` representing the current :app:`Pyramid` request. Passing a request keyword argument will cause the ``render_to_response`` function to supply the renderer with more correct system values (see -:ref:`renderer_system_values`), because most of the information -required to compose proper system values is present in the request. -If you care about the correct system values being provided to the -renderer being called (in particular, if your template relies on the -name ``request`` or ``context``, or if you've configured special -:term:`renderer globals` make sure to pass ``request`` as a keyword -argument in every call to to a ``pyramid.renderers.render_*`` -function. +:ref:`renderer_system_values`), because most of the information required +to compose proper system values is present in the request. If your +template relies on the name ``request`` or ``context``, or if you've +configured special :term:`renderer globals`, make sure to pass +``request`` as a keyword argument in every call to to a +``pyramid.renderers.render_*`` function. Every view must return a :term:`response` object (except for views which use a :term:`renderer` named via view configuration, which we'll -- cgit v1.2.3