Fixed #24906 -- Fixed ResolverMatch.app_name for nested namespaces.

Set ResolverMatch.app_name to the full path of nested application
namespaces.
This commit is contained in:
Marten Kenbeek 2015-06-03 19:12:27 +02:00 committed by Tim Graham
parent 1ea87c8c79
commit bc77eb6d08
5 changed files with 44 additions and 20 deletions

View file

@ -155,6 +155,15 @@ If the URL does not resolve, the function raises a
The application namespace for the URL pattern that matches the
URL.
.. attribute:: ResolverMatch.app_names
.. versionadded:: 1.9
The list of individual namespace components in the full
application namespace for the URL pattern that matches the URL.
For example, if the ``app_name`` is ``'foo:bar'``, then ``app_names``
will be ``['foo', 'bar']``.
.. attribute:: ResolverMatch.namespace
The instance namespace for the URL pattern that matches the

View file

@ -597,6 +597,13 @@ Miscellaneous
:attr:`~django.test.SimpleTestCase.allow_database_queries` class attribute
to ``True`` on your test class.
* :attr:`ResolverMatch.app_name
<django.core.urlresolvers.ResolverMatch.app_name>` was changed to contain
the full namespace path in the case of nested namespaces. For consistency
with :attr:`ResolverMatch.namespace
<django.core.urlresolvers.ResolverMatch.namespace>`, the empty value is now
an empty string instead of ``None``.
.. _deprecated-features-1.9:
Features deprecated in 1.9