#29008: When DEBUG is True, raising Http404 in a path converter's to_python
method
does not result in a technical response
------------------------------------------+------------------------
Reporter: Antoine Humeau | Owner: nobody
Type: Bug | Status: new
Component: Core (URLs) | Version: 2.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+------------------------
This is the response I get (plain text):
{{{
A server error occurred. Please contact the administrator.
}}}
I understand a `ValueError` should be raised which tells the URL resolver
"this path does not match, try next one" but `Http404` is what came to my
mind intuitively and the error message was not very helpful.
One could also make a point that raising a `Http404` should be valid way
to tell the resolver "this is indeed the right path but the current
parameter value does not match anything so stop what you are doing and let
the handler return the 404 page (including a helpful error message when
DEBUG is True instead of the default 'Django tried these URL patterns')".
This would prove useful for example to implement a path converter that
uses `get_object_or_404`.
--
Ticket URL: <https://code.djangoproject.com/ticket/29008>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.d14e7b1645a0dd8bd1a282674b8593c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
