#29744: Optimization: Multiple URLResolvers may be unintentionally be
constructed
by calls to `django.urls.resolvers.get_resolver`
-------------------------------------+-------------------------------------
Reporter: Benjamin Woodruff | Owner: Benjamin
Type: | Woodruff
Cleanup/optimization | Status: closed
Component: Core (URLs) | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"54dcfbc36780054d39299bfd1078938e5dd4e839" 54dcfbc3]:
{{{
#!CommitTicketReference repository=""
revision="54dcfbc36780054d39299bfd1078938e5dd4e839"
Fixed #29744 -- Fixed caching of URLResolver for a default URLconf.
get_resolver() for a default URLconf (passing no argument) and for
settings.ROOT_URLCONF should return the same cached object.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29744#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/061.ba7d38a6574165c99fe108f7bc71640e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
