#15849: {% ifchanged %} not thread-safe
------------------------------------+---------------------------------
Reporter: akaihola | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Template system
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 1
Patch needs improvement: 0 | Easy pickings: 0
------------------------------------+---------------------------------
Comment (by akaihola):
Replying to [comment:4 carljm]:
> I could see an argument that automated tests for template tag thread-
safety or more difficult than they are worth, but I think we should at
least have the argument ;-)
I found an existing [http://code.djangoproject.com/changeset/8306#file3
thread-safety test case] in the Django test suite. It's for bug #4948
("Saving !FileField files is not thread-safe"). Martin von Löwis also
[http://code.djangoproject.com/ticket/4948#comment:14 described in a
comment] how his
[http://code.djangoproject.com/attachment/ticket/4948/t.py example script]
demonstrated the bug.
Do you think a similar approach could be used for testing template tags?
--
Ticket URL: <http://code.djangoproject.com/ticket/15849#comment:5>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
