#28413: app_name doesn't work in ROOT_URLCONF
-----------------------------+--------------------------------------
Reporter: stephanm | Owner: nobody
Type: Bug | Status: closed
Component: Core (URLs) | Version: 1.11
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by Marten Kenbeek):
* status: new => closed
* resolution: => invalid
Comment:
Replying to [comment:1 Tim Graham]:
> I think the issue is that `app_name` isn't supported in `ROOT_URLCONF`.
I'm not sure if it makes sense to support that.
That's right, `app_name` is only supported in included urlconfs.
URL namespaces are designed to prevent naming conflicts between included
urlconfs, and to allow the deployment of more than one instance of a
specific urlconf. Adding a namespace to the root urlconf only has the
cosmetic effect that you need to prepend ''every'' viewname with that
namespace when reversing, it does not help with naming conflicts or
multiple deployments. I don't think it makes sense to support this.
I'm closing this as invalid as it is certainly not a bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/28413#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.aab1af867f6a8f56976ef372b58b9f53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
