summaryrefslogtreecommitdiff
path: root/docs/narr/templates.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2012-09-13 02:05:19 -0400
committerChris McDonough <chrism@plope.com>2012-09-13 02:05:19 -0400
commitb72ba1a98ebc6fc6c8d9a11ab1c340b89015e644 (patch)
treea33c69dc71addf70cd1871af609282f337dee8fb /docs/narr/templates.rst
parentdc8b49f436e3d249c6c9440cf2c1b74acf4a8ad8 (diff)
downloadpyramid-b72ba1a98ebc6fc6c8d9a11ab1c340b89015e644.tar.gz
pyramid-b72ba1a98ebc6fc6c8d9a11ab1c340b89015e644.tar.bz2
pyramid-b72ba1a98ebc6fc6c8d9a11ab1c340b89015e644.zip
add upgrading chapter, make docs render again
Diffstat (limited to 'docs/narr/templates.rst')
-rw-r--r--docs/narr/templates.rst30
1 files changed, 6 insertions, 24 deletions
diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst
index 656cf4773..9a825c2ab 100644
--- a/docs/narr/templates.rst
+++ b/docs/narr/templates.rst
@@ -46,20 +46,6 @@ within the body of a view callable like so:
{'foo':1, 'bar':2},
request=request)
-.. warning::
-
- Earlier iterations of this documentation
- (pre-version-1.3) encouraged the application developer to use
- ZPT-specific APIs such as
- :func:`pyramid.chameleon_zpt.render_template_to_response` and
- :func:`pyramid.chameleon_zpt.render_template` to render templates
- directly. This style of rendering still works, but at least for
- purposes of this documentation, those functions are deprecated.
- Application developers are encouraged instead to use the functions
- available in the :mod:`pyramid.renderers` module to perform
- rendering tasks. This set of functions works to render templates
- for all renderer extensions registered with :app:`Pyramid`.
-
The ``sample_view`` :term:`view callable` function above returns a
:term:`response` object which contains the body of the
``templates/foo.pt`` template. In this case, the ``templates``
@@ -79,12 +65,12 @@ prefix on Windows.
.. warning::
Only :term:`Chameleon` templates support defining a renderer for a
- template relative to the location of the module where the view
- callable is defined. Mako templates, and other templating system
- bindings work differently. In particular, Mako templates use a
- "lookup path" as defined by the ``mako.directories`` configuration
- file instead of treating relative paths as relative to the current
- view module. See :ref:`mako_templates`.
+ template relative to the location of the module where the view callable is
+ defined. Mako templates, and other templating system bindings work
+ differently. In particular, Mako templates use a "lookup path" as defined
+ by the ``mako.directories`` configuration file instead of treating
+ relative paths as relative to the current view module. See
+ :ref:`mako_templates`.
The path can alternately be a :term:`asset specification` in the form
``some.dotted.package_name:relative/path``. This makes it possible to
@@ -600,10 +586,6 @@ When the template is rendered, it will show:
Hello, world!
-If you'd rather use templates directly within a view callable (without
-the indirection of using a renderer), see :ref:`chameleon_text_module`
-for the API description.
-
See also :ref:`built_in_renderers` for more general information about
renderers, including Chameleon text renderers.