#32105 closed New feature (fixed)
Allow overriding technical 500 page templates
Reported by: | Aarni Koskela | Owned by: | Aarni Koskela |
---|---|---|---|
Component: | Error reporting | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When specifying a custom DEFAULT_EXCEPTION_REPORTER
class, the template paths aren't easily overrideable since they're formed as local variables within the rendering functions (see https://github.com/django/django/blob/78ae8cc5d8aff65afbf35947421a8a1aba13bfab/django/views/debug.py#L334); as it is, one has to copy-paste the functions into a subclass.
Hoisting them up to class-level variables would make deriving from the default ExceptionReporter
more effortless.
Change History (8)
comment:1 by , 4 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:3 by , 4 years ago
Needs documentation: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
Yep, seems reasonable. The new attributes will need docs and release notes.
comment:4 by , 4 years ago
Needs documentation: | unset |
---|
comment:5 by , 4 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
I have a patch for this, will rebase and clean up (https://github.com/django/django/pull/12393).