#34451: Incorrect exception handling within the django exception handler
---------------------------------+----------------------------------------
Reporter: Michael Galler | Owner: Akshat verma
Type: Bug | Status: assigned
Component: Error reporting | Version: 4.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Changes (by Mariusz Felisiak):
* component: Core (Other) => Error reporting
* stage: Unreviewed => Accepted
Comment:
> If I interpret this correctly, the problem is that the exception handler
tries to render the 500 page, which imports the urls which leads to the
same error.
Tentatively accepted for future investigation. It seems that at least
`resolve_error_handler()`/`get_caller()` should handle errors when
checking the URLconf/resolving paths.
--
Ticket URL: <https://code.djangoproject.com/ticket/34451#comment:6>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018745bfd8aa-ce1aee98-3771-45b3-a3e7-3a522a1a53a0-000000%40eu-central-1.amazonses.com.
