summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBaptiste Mispelon <bmispelon@gmail.com>2014-07-29 10:54:11 +0200
committerBaptiste Mispelon <bmispelon@gmail.com>2014-07-29 10:56:24 +0200
commit62c74abbb06a081708c2cb5cc459f39beb26acaa (patch)
tree15876e67579e0de4aea37c221a6a0f7b31c5eca6
parentd6e73a876d77e889efe839345d39690a7004e2f4 (diff)
Fixed #23114 -- Clarified documentation of template lookups.
Thanks to gmunumel and Tom Dalton for their help on the patch.
-rw-r--r--docs/topics/templates.txt14
1 files changed, 8 insertions, 6 deletions
diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
index 92114aebe5..e50e7c96f7 100644
--- a/docs/topics/templates.txt
+++ b/docs/topics/templates.txt
@@ -95,13 +95,15 @@ Use a dot (``.``) to access attributes of a variable.
following lookups, in this order:
* Dictionary lookup
- * Attribute lookup
- * Method call
- * List-index lookup
+ * Attribute or method lookup
+ * Numeric index lookup
- This can cause some unexpected behavior with objects that override
- dictionary lookup. For example, consider the following code snippet that
- attempts to loop over a ``collections.defaultdict``::
+ If the resulting value is callable, it is called with no arguments. The
+ result of the call becomes the template value.
+
+ This lookup order can cause some unexpected behavior with objects that
+ override dictionary lookup. For example, consider the following code snippet
+ that attempts to loop over a ``collections.defaultdict``::
{% for k, v in defaultdict.iteritems %}
Do something with k and v here...