#15791: New feature: callable objects can signal that templates should never
call
them
---------------------------------------+-------------------------------
Reporter: ejucovy | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Template system
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
---------------------------------------+-------------------------------
Comment (by ejucovy):
It would be nice if there were also a way to signal this from the
templates themselves, perhaps with a `{{variable|nocall}}` filter or a `{%
nocall %} .. {% endnocall %}` block tag. I'm not sure if the former is
even possible (since the variable would usually be called before the
filter is applied) but the latter might be. A template-driven approach
would have the advantage of not requiring direct access to the object's
attributes, which can be inconvenient in some circumstances (e.g. fetching
large batches of callable objects whose interface is defined in a third-
party library)
--
Ticket URL: <http://code.djangoproject.com/ticket/15791#comment:2>
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.
