p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Clarify the description of URL namespacing. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11288 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2009-07-22 01:41:16 +00:00
parent d33386c584
commit 84d86c07e0
1 changed files with 15 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
docs/releases/1.1-rc-1.txt
View File

@ -24,12 +24,11 @@ such use is discouraged.
What's new in Django 1.1 RC 1 What's new in Django 1.1 RC 1
============================= =============================
The Django codebase has been in feature freeze since the first 1.1 The Django codebase has -- with one exception -- been in feature
beta release, and so this release candidate contains only one new freeze since the first 1.1 beta release, and so this release candidate
feature (introduced as part of the resolution of a larger bug; see contains only one new feature (see below); work leading up to this
below for a description); work leading up to this release candidate release candidate has instead been focused on bugfixing, particularly
has instead been focused on bugfixing, particularly on the new on the new features introduced prior to the 1.1 beta.
features introduced prior to the 1.1 beta.
For an overview of those features, consult :ref:`the Django 1.1 beta For an overview of those features, consult :ref:`the Django 1.1 beta
release notes <releases-1.1-beta-1>`. release notes <releases-1.1-beta-1>`.
@ -40,22 +39,17 @@ URL namespaces
The 1.1 beta release introduced the ability to use reverse URL The 1.1 beta release introduced the ability to use reverse URL
resolution with Django's admin application, which exposed a set of resolution with Django's admin application, which exposed a set of
:ref:`named URLs <naming-url-patterns>`. This feature still exists, :ref:`named URLs <naming-url-patterns>`. Unfortunately, achieving
but in order to provide consistent resolution of admin URLs, including consistent and correct reverse resolution for admin URLs proved
support for multiple :class:`~django.contrib.admin.AdminSite` objects extremely difficult, and so one additional feature was added to Django
in use in a single installation, a new feature has been introduced: to resolve this issue: URL namespaces.
URL "namespaces".
This takes the form of an additional supported argument -- In short, this feature allows the same group of URLs, from the same
``namespace`` -- to the ``include()`` function used to include groups application, to be included in a Django URLConf multiple times, with
of URL patterns in a Django URLConf. When this argument is used, varying (and potentially nested) named prefixes which will be used
pattern names supplied for reverse resolution may specify the when performing reverse resolution. For full details, see :ref:`the
namespace in addition to the pattern name (using a colon as separator; documentation on defining URL namespaces
e.g., ``namespace-name:pattern-name``), and the reverse resolver will <topics-http-defining-url-namespaces>`.
take the namespace into account when searching for a match.
For more details, see :ref:`the documentation on defining URL
namespaces <topics-http-defining-url-namespaces>`.
Due to the changes needed to support this feature, the URL pattern Due to the changes needed to support this feature, the URL pattern
names used when reversing admin URLs have changed since the 1.1 beta names used when reversing admin URLs have changed since the 1.1 beta