#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 Tom Forbes):
By the majority use case I meant people that simply want to have the same
template settings across production and development settings, rather than
duplicating pretty much the same configuration. We do loose the speed
benefit but we never really had it in the first place as (I believe) very
few people used the cached loader in development due to this very issue.
That being said, having re-read the comments here I'm not sure if that
really is the majority use case or just me (in my experience development
is fast enough, but the two slightly different settings is annoying).
The autoreloader is flexible enough to subscribe to template changes, but
the issue is that it's really not simple to do at the cached template
loader level as everything is pretty abstract (and quite rightly so). Also
we run into an issue where the loaders are not actually imported until the
first template is rendered which means that the initial autoreloader
started signal is not correctly registered.
I will see if I can find a better implementation, but the import issue is
especially annoying.
--
Ticket URL: <https://code.djangoproject.com/ticket/25791#comment:13>
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.0fd0232c07b0be966acd3305c8115114%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
