Added release note and updated TEMPLATE_DEBUG documentation for r16833. Thanks...

Default: ``False``

A boolean that turns on/off template debug mode. If this is ``True``, the fancy

error page will display a detailed report for any ``TemplateSyntaxError``. This

report contains the relevant snippet of the template, with the appropriate line

highlighted.

error page will display a detailed report for any exception raised during

template rendering. This report contains the relevant snippet of the template,

with the appropriate line highlighted.

Note that Django only displays fancy error pages if :setting:`DEBUG` is ``True``, so

you'll want to set that to take advantage of this setting.

See the :meth:`~django.db.models.query.QuerySet.bulk_create` docs for more

information.

No wrapping of exceptions in ``TEMPLATE_DEBUG`` mode

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In previous versions of Django, whenever the :setting:`TEMPLATE_DEBUG` setting

was ``True``, any exception raised during template rendering (even exceptions

unrelated to template syntax) were wrapped in ``TemplateSyntaxError`` and

re-raised. This was done in order to provide detailed template source location

information in the debug 500 page.

In Django 1.4, exceptions are no longer wrapped. Instead, the original

exception is annotated with the source information. This means that catching

exceptions from template rendering is now consistent regardless of the value of

:setting:`TEMPLATE_DEBUG`, and there's no need to catch and unwrap

``TemplateSyntaxError`` in order to catch other errors.

Minor features

~~~~~~~~~~~~~~