#27597: UrlResolver doesn't check all possibilities
------------------------------+--------------------------------------
Reporter: Adrien mille | Owner: nobody
Type: Bug | Status: new
Component: Core (URLs) | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by Marten Kenbeek):
According to the [https://docs.djangoproject.com/en/1.10/topics/http/urls
/#url-namespaces docs]:
> **instance namespace**
>
> This identifies a specific instance of an application. Instance
namespaces **should be unique** across your entire project.
I believe that's what's happening here. You have multiple includes with
the exact same instance namespace, while Django expects that there is only
one. So I don't think it's a bug in Django.
I'm not sure whether this is actually desirable behaviour, or what kind of
impact changing it would have on existing projects. If we keep it as is,
it may be a good idea to add a system check that checks if instance
namespaces are indeed unique across the project.
--
Ticket URL: <https://code.djangoproject.com/ticket/27597#comment:4>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.793b4981958a9861f13d84518f115272%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
