#20945: Allow cache tag to use specified cache config.
---------------------------------+--------------------
Reporter: FunkyBob | Owner: nobody
Type: New feature | Status: new
Component: Template system | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 1 | UI/UX: 0
---------------------------------+--------------------
Currently the cache tag will use the default cache - always.
However, the staticfiles app, for instance, can be configured as to which
it will use.
I propose the following:
1. Add a new setting (called DEFAULT_TEMPLATE_FRAGMENT_CACHE in the PR) to
specify which to use by default.
2. Extend the cache tag to allow the last argument to be using="cache
name", falling back to the default if it doesn't exist.
Current code is:
https://github.com/django/django/pull/1490
I'm just working on the tests and final documentation updates.
--
Ticket URL: <https://code.djangoproject.com/ticket/20945>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.db4d2653cf495f5933be811d1ee4331d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
