#15025: Different template rendering semantics since r14992
--------------------------------------+-------------------------------------
Reporter: donspaulding | Owner: nobody
Status: new | Milestone: 1.3
Component: Template system | Version: SVN
Resolution: | Keywords: blocker, regression
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by mrmachine):
* milestone: => 1.3
Comment:
Looking at [14992], I believe that the problem is only on the debug page.
When rendering normal templates, any template variable resolution that
raises an exception *should* raise it loudly if the exception doesn't
explicitly have an attribute `silent_variable_failure` which is `True`.
The exception should then be displayed on the debug page or emailed to the
developer, etc.
The problem now with the debug page is that it is resolving local vars for
each stack frame as template vars, which transforms the variable in the
case of a callable. Besides possibly raising exceptions and crashing the
debug page, this is incorrect behaviour for the debug page which should
only be showing the `__repr__` for stack frame local vars, not evaluating
and transforming them.
For example, if your view has a variable `form_class` which is a subclass
of `django.forms.Form`, the debug page should display this as a form class
and not as an unbound form instance.
--
Ticket URL: <http://code.djangoproject.com/ticket/15025#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
