#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
-------------------------------------+-------------------------------------
Changes (by Tom Forbes):
* needs_better_patch: 1 => 0
Comment:
I'm not sure what to do about the registrations. I don't hate the way I've
currently done it, and I don't really see it as a big problem to be
honest. We just have an `autoreload` module imported in the
`django.template` namespace 🤷♀️.
I'm happy to do it another way, but I can't think of one and nothing has
been suggested so far. So I'm going to unmark this as PNI for now.
--
Ticket URL: <https://code.djangoproject.com/ticket/25791#comment:18>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.a00d370faa19df9106126d24a371aade%40djangoproject.com.
