Author: russellm
Date: 2010-05-09 00:48:06 -0500 (Sun, 09 May 2010)
New Revision: 13161
Modified:
django/trunk/docs/topics/http/urls.txt
Log:
Fixed #13051 -- Corrected the documentation of URL namespacing to match the
tested implementation behavior. Thanks to apollo13 for the report, and Gabriel
Hurley for the patch.
Modified: django/trunk/docs/topics/http/urls.txt
===================================================================
--- django/trunk/docs/topics/http/urls.txt 2010-05-09 05:47:35 UTC (rev
13160)
+++ django/trunk/docs/topics/http/urls.txt 2010-05-09 05:48:06 UTC (rev
13161)
@@ -728,7 +728,7 @@
that has an instance namespace matching the application namespace (in
this example, an instance of the ``myapp`` called ``myapp``).
- 4. If there is no default application instance, Django will pick the first
+ 4. If there is no default application instance, Django will pick the last
deployed instance of the application, whatever its instance name may be.
5. If the provided namespace doesn't match an application namespace in
@@ -749,9 +749,9 @@
the instance ``bar``.
* If there is no current instance - say, if we were rendering a page
- somewhere else on the site - ``myapp:index`` will resolve to the first
+ somewhere else on the site - ``myapp:index`` will resolve to the last
registered instance of ``myapp``. Since there is no default instance,
- the first instance of ``myapp`` that is registered will be used. This
could
+ the last instance of ``myapp`` that is registered will be used. This
could
be ``foo`` or ``bar``, depending on the order they are introduced into
the
urlpatterns of the project.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
