#22055: 404 page does not display stack trace when Resolver404 is raised from a
view
-------------------------------+--------------------------------------
Reporter: gnosek | Owner: gnosek
Type: Uncategorized | Status: new
Component: Core (URLs) | Version: 1.6
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by gnosek):
* status: closed => new
* resolution: wontfix =>
Comment:
See #18373 for the use case.
If you're calling resolve('/some-url') that fails, you're not raising an
Http404 explicitly. It's just a function call that fails, just like the
ORM or whatever.
I agree that manually raised Http404s should not trigger the stack trace
and this ticket is not about it. It's just about treating exceptions from
resolve() failure just like every other exception.
IMO, the right thing to do is:
* Failing to resolve an URL from Django core -> no stack trace
* Raising Http404 from a view -> no stack trace
* Failing to resolve an URL from a view -> stack trace (and arguably 500
response code but there's backwards compatibility to worry about)
--
Ticket URL: <https://code.djangoproject.com/ticket/22055#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.6384209efa8b1a1a14b193e449344849%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
