#25094: Jinja2 backend requires settings to be configured
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: nobody
Type: Uncategorized | Status: new
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: jinja2 cache | Triage Stage:
backend | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
We're trying to keep as many modules as possible importable without
requiring configured settings.
IIRC there was another ticket recently to stop accessing settings at
import time when importing `django.core.caches`. This is the correct
approach. The technique proposed here will fix the symptoms for
`template.backends.utils` but not for any other module that imports
`django.core.caches`. I recommend to close this as a duplicate of the
other ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/25094#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 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/063.9f1044eb83eb4d64f3dac208aeb22add%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
