#15025: Different template rendering semantics since r14992
--------------------------------------+-------------------------------------
Reporter: donspaulding | Owner: nobody
Status: new | Milestone:
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 ramiro):
* keywords: => blocker, regression
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
I've also seen this while working on #11715, the problem can also be
reproduced with the test case posted by the reporter there.
One where this problem seems to be happening is rendering of the page when
500 error is raised and if `DEBUG` is True, some callables are run that
weren't before, and that generates other exception because at that point
classes are instantiated that aren't supposed to be (e.g. ModelForms).
If ones goes back to r14991 the 500 usual error page is generated
reporting the correct error and showing an useful traceback.
There have been one report in the django-user list as well:
https://groups.google.com/d/topic/django-users/8TGK7PvDD3Y/discussion
--
Ticket URL: <http://code.djangoproject.com/ticket/15025#comment:1>
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.
