Don't know if my last message made it to the mailing list, it looks like
google-group might have eaten it. If it's not the case sorry for the noise.
Concerning (2) I do agree with Carl it's not required to default to a
specific template fragment cache alias. For the uncommon cases you want to
cache template fragments using another cache backend a simple template
context processor should do:
# context_processors.py
def template_cache(context):
context['template_cache']
# template.html
{% cache using=template_cache %}...{% endcache %}
Le mercredi 21 août 2013 08:05:58 UTC-4, Curtis Maloney a écrit :
>
> Was just after some more eyes and opinions on
> https://code.djangoproject.com/ticket/20945
>
> Current PR is at: https://github.com/django/django/pull/1490
>
> This patch does two things:
>
> 1) it allows specifying on a {% cache %} tag which cache to use
>
> {% cache ..... using="cachename" %}
>
> 2) it makes the cache tag try to use a cache called "template_fragments"
> if it exists, and otherwise use "default"
>
> This is following on from the pattern established in staticfiles, where
> the CachedFilesMixin will try to use a cache called "staticfiles" if
> available.
>
> So far everyone involved agrees with (1)
>
> However, the reception of (2) has so far been... luke warm.
>
> So I was hoping for more eyes/input on this...
>
> --
> Curtis
>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.
