Fixed #21044 -- Documented django.core.urlresolvers.Resolver404
Thanks Keryn Knight for the suggestion.
This commit is contained in:
parent
7b62b80693
commit
eacf060e01
|
@ -131,6 +131,15 @@ URL Resolver exceptions
|
||||||
|
|
||||||
URL Resolver exceptions are defined in :mod:`django.core.urlresolvers`.
|
URL Resolver exceptions are defined in :mod:`django.core.urlresolvers`.
|
||||||
|
|
||||||
|
Resolver404
|
||||||
|
--------------
|
||||||
|
.. exception:: Resolver404
|
||||||
|
|
||||||
|
The :exc:`Resolver404` exception is raised by
|
||||||
|
:func:`django.core.urlresolvers.resolve()` if the path passed to
|
||||||
|
``resolve()`` doesn't map to a view. It's a subclass of
|
||||||
|
:class:`django.http.Http404`
|
||||||
|
|
||||||
NoReverseMatch
|
NoReverseMatch
|
||||||
--------------
|
--------------
|
||||||
.. exception:: NoReverseMatch
|
.. exception:: NoReverseMatch
|
||||||
|
|
|
@ -102,8 +102,9 @@ worry about the ``urlconf`` parameter. The function returns a
|
||||||
:class:`ResolverMatch` object that allows you
|
:class:`ResolverMatch` object that allows you
|
||||||
to access various meta-data about the resolved URL.
|
to access various meta-data about the resolved URL.
|
||||||
|
|
||||||
If the URL does not resolve, the function raises an
|
If the URL does not resolve, the function raises a
|
||||||
:class:`~django.http.Http404` exception.
|
:exc:`~django.core.urlresolvers.Resolver404` exception (a subclass of
|
||||||
|
:class:`~django.http.Http404`) .
|
||||||
|
|
||||||
.. class:: ResolverMatch
|
.. class:: ResolverMatch
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue