#31547: A bug in Django3.0.6 about the function of "include"
---------------------------------+--------------------------------------
Reporter: Xiang Li | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: master
Severity: Release blocker | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
This is the expected behavior.
See [https://docs.djangoproject.com/en/3.0/ref/urls/#include the include
docs]. It provided 3 calling patterns. Where you pass the `app_namespace`
(`app_name` in your case) the first parameter is a tuple.
If you use the first pattern `include(module)`, `app_name` will be pulled
from the included module,
[https://docs.djangoproject.com/en/3.0/topics/http/urls/#url-namespaces-
and-included-urlconfs as described here].
--
Ticket URL: <https://code.djangoproject.com/ticket/31547#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.3d1d6aebb8103829fc3942b0b8f8c4b6%40djangoproject.com.
