#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: invalid
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 Enrico Zini):
From what I could see, "Set the URLconf for the current thread" in
`set_urlconf`'s docstring looks like a leftover from the pre-async times
and could become "Set the URLconf for the current thread or asyncio task".
I understand it's not a public API and indeed I only set `request.urlconf`
in my code. We spotted the docstring while trying to double check the
validity of what we were designing on the async case, and had some extra
digging to do to reassure ourselves we were still doing the right thing,
hence this issue.
I'm surprised the ticket got closed, but fair enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/35807#comment:3>
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/0107019265f8abc2-cd6eb27a-64ba-448a-b8ea-0a0b4da0306f-000000%40eu-central-1.amazonses.com.
