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

Set ResolverMatch.app_name to the full path of nested application
namespaces.

2 files changed, 16 insertions, 0 deletions

diff --git a/docs/ref/urlresolvers.txt b/docs/ref/urlresolvers.txt
index 79c219a8d8..60a6192a90 100644
--- a/docs/ref/urlresolvers.txt
+++ b/docs/ref/urlresolvers.txt
@@ -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
diff --git a/docs/releases/1.9.txt b/docs/releases/1.9.txt
index 6b42418ee4..2ee1dae246 100644
--- a/docs/releases/1.9.txt
+++ b/docs/releases/1.9.txt
@@ -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