Opened 18 years ago
Closed 18 years ago
#2773 closed defect (wontfix)
django.views.defaults.server_error should use RequestContext
Reported by: | Owned by: | Jacob | |
---|---|---|---|
Component: | Generic views | Version: | |
Severity: | minor | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Context created by the configured context processors is not made available to the standard 500 error page.
Attached a patch, it's a one line change and pretty brainless so no tests.
Attachments (1)
Change History (3)
by , 18 years ago
Attachment: | 2773.patch added |
---|
comment:1 by , 18 years ago
IIRC this has come up before and was vetoed on the grounds that we should, as far as possible, reduce the number of things that could possibly raise another exception once we're into the 500-handling, but I don't have a reference to it off the top of my head.
comment:2 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Yeah, just found it: Adrian reverted RequestContext
out of the 500 view in [3193]. Going ahead and marking this wontfix because of that.
Patch to modify django.views.defaults.server_error to pass RequestContext to Template.render()