Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fixed #20962 -- Documented that template tag render() may raise excep…

…tions.

Thanks Keryn Knight for the report.
  • Loading branch information...
commit e077224f4ad69a68ae58a373ef69941272d3656c 1 parent 54cd930
@Bouke Bouke authored timgraham committed
Showing with 7 additions and 2 deletions.
  1. +1 −0  AUTHORS
  2. +6 −2 docs/howto/custom-template-tags.txt
View
1  AUTHORS
@@ -277,6 +277,7 @@ answer newbie questions, and generally made Django that much better:
Janos Guljas
Thomas Güttler <hv@tbz-pariv.de>
Horst Gutmann <zerok@zerokspot.com>
+ Bouke Haarsma <bouke@haarsma.eu>
Antti Haapala <antti@industrialwebandmagic.com>
Scot Hacker <shacker@birdhouse.org>
dAniel hAhler
View
8 docs/howto/custom-template-tags.txt
@@ -478,8 +478,12 @@ Notes:
* The ``render()`` method is where the work actually happens.
-* ``render()`` should never raise ``TemplateSyntaxError`` or any other
- exception. It should fail silently, just as template filters should.
+* ``render()`` should generally fail silently, particularly in a production
+ environment where :setting:`DEBUG` and :setting:`TEMPLATE_DEBUG` are
+ ``False``. In some cases however, particularly if :setting:`TEMPLATE_DEBUG` is
+ ``True``, this method may raise an exception to make debugging easier. For
+ example, several core tags raise ``django.template.TemplateSyntaxError``
+ if they receive the wrong number or type of arguments.
Ultimately, this decoupling of compilation and rendering results in an
efficient template system, because a template can render multiple contexts
Please sign in to comment.
Something went wrong with that request. Please try again.