#15849: {% ifchanged %} not thread-safe
-------------------------------------+-------------------------------------
Reporter: akaihola | Owner: bpeschier
Type: Bug | Status: closed
Component: Template system | Version: master
Severity: Normal | Resolution: fixed
Keywords: sprint2013 | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 1
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Florian Apolloner <florian@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"8503120c1024ad7ec2151196a743d6daec21334b"]:
{{{
#!CommitTicketReference repository=""
revision="8503120c1024ad7ec2151196a743d6daec21334b"
Fixed #15849 -- Made IfChanged node thread safe.
Previously, the ifchanged node stored state on `self._last_seen`,
thereby giving undesired results when the node is reused by another
thread at the same time (e.g. globally caching a Template object).
Thanks to akaihola for the report and Diederik van der Boor and
Bas Peschier for the patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15849#comment:14>
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.
For more options, visit https://groups.google.com/groups/opt_out.
