#25791: Implement autoreload behaviour for cached template loader
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: nobody
Type: New feature | Status: new
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: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: 0 => 1
* stage: Someday/Maybe => Accepted
Comment:
Aymeric suggests:
The proposed patch for auto-reloading doesn’t seem too bad in terms of
complexity. Its main drawback is that it add a new auto-reload mechanism,
distinct from django.utils.autoreload.
[[BR]]
I would prefer to trigger the autoreloader on template file changes to
make it easier to switch e.g. to watchman in the future.
--
Ticket URL: <https://code.djangoproject.com/ticket/25791#comment:7>
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.9f4f3b6e46f763c60bb3f18572e0f00e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
