summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-11-29 20:49:35 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-11-29 20:49:35 -0700
commit9794d3e872c40744466ceccb113bd3d5f0b795a5 (patch)
tree76b36cdcf19793ed836c90eb543df4f94f8380d5 /docs
parentf7c539d9cc33c91d3da2d3022da1b92ff99412c1 (diff)
downloadpyramid-9794d3e872c40744466ceccb113bd3d5f0b795a5.tar.gz
pyramid-9794d3e872c40744466ceccb113bd3d5f0b795a5.tar.bz2
pyramid-9794d3e872c40744466ceccb113bd3d5f0b795a5.zip
reword paragraph for clarity
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/views.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index dc1d139a5..79d3b9489 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -573,13 +573,13 @@ The dictionary items will then be used in the global template space. If the
view callable returns anything but a Response object, or a dictionary, an error
will be raised.
-A Mako template can be specified two ways using the ``renderer`` attribute.
-First, a relative path can be used to name a
-Mako template relative to the configured Mako template directories. Second, a
-:term:`resource specification` can be used to locate a template to render.
-These two styles of naming a template to render also carry through to Mako
-templates, so that Mako template's can inherit using a :term:`resource
-specification` if desired.
+When using a ``renderer`` argument to a :term:`view configuration` to
+specify a Mako template, the value of the ``renderer`` may be a path
+relative to the ``mako.directories`` setting (e.g.
+``some/template.mak``) or, alternately, it may be a :term:`resource
+specification` (e.g. ``apackage:templates/sometemplate.mak``). Mako
+templates may internally inherit other Mako templates using a relative
+filename or a :term:`resource specification` as desired.
Here's an example view configuration which uses a relative path: