#26507: Add autoreloading to the cached template loader
---------------------------------+--------------------------------------
Reporter: srkunze | Owner: nobody
Type: New feature | Status: closed
Component: Template system | Version: master
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by srkunze):
Thanks Tim for finding the related issue.
I don't know if I would agree with the new title. Actually, I do not want
to reload/replace the already loaded template.
Looking at the source, I would say, we could make 'Loader.cache_key'
respect the mtime of the first found template.
So, they are two versions of the template in the cache but a cache does
not need to be perfect after all and the increased memory footprint would
not even matter in development.
--
Ticket URL: <https://code.djangoproject.com/ticket/26507#comment:2>
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/065.a3cb96feccf23ad6171e19c0f2a7baf1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
