#35807: Clarify django.urls.set_urlconf scoping behaviour
-------------------------------+--------------------------------------
Reporter: Enrico Zini | Owner: (none)
Type: Uncategorized | Status: closed
Component: Documentation | Version: 5.0
Severity: Normal | Resolution: needsinfo
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 Sarah Boyce):
* cc: Andrew Godwin, Carlton Gibson (added)
* resolution: => needsinfo
* status: new => closed
Comment:
I'm struggling to follow what this is asking for - can you share an
example of the behavior you're seeing?
From what I can see, both async and sync requests handle the urlconf the
same - it is the ROOT_URLCONF unless set by a middleware
[https://docs.djangoproject.com/en/dev/topics/http/urls/#how-django-
processes-a-request as documented].
--
Ticket URL: <https://code.djangoproject.com/ticket/35807#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/0107019265d957bc-9699cd7d-164c-4e17-a33f-fe347a278771-000000%40eu-central-1.amazonses.com.
