#14926: Support nesting app namespaces with current_app
------------------------------------+---------------------------------------
Reporter: dcramer | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.2
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not sure I follow the advantage here. current_app isn't being provided
as a prefix; it's context in which the URL name should be interpreted. For
example, there can be multiple admin app namespaces deployed; current_app
is used to define which instance of the admin app should be used.
Closing invalid; there isn't enough detail here to establish the API or
functionality that is being requested.
--
Ticket URL: <http://code.djangoproject.com/ticket/14926#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
