#24516: make_template_fragment_key behaves differently than the {% cache %}
template tag for the "None" value
-------------------------------------+--------------------------------
Reporter: wetneb | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: 1.7
Severity: Normal | Keywords: cache, templatetag
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+--------------------------------
The function make_template_fragment_key in django.core.cache.utils can be
used to compute the cache key associated with a given template fragment.
When one of the parameters of this cache fragment get the value None, this
function translates internally this value to 'None' (the string), whereas
the template tag translates it to the empty string.
A patch for this bug can be found on the following branch:
http://github.com/wetneb/django
--
Ticket URL: <https://code.djangoproject.com/ticket/24516>
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/049.05805be45b8bb13ef66a75fec1f5205c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.