#25791: Implement autoreload behaviour for cached template loader
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Tom
| Forbes
Type: New feature | Status: assigned
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: autoreload | Triage Stage: Accepted
templates cached loader |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
Can you explain what you mean by the "majority use case"? The benefit
seems to be that you can use the same `TEMPLATES` settings in development
and production (although #25788 already helps with that). The downside is
that you can no longer get the speed benefit of the cached template loader
in development.
--
Ticket URL: <https://code.djangoproject.com/ticket/25791#comment:12>
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.562887d5abf1ee03d7071cca4d9c7e5e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
