Ticket #7374: docs-simpletag.diff

docs/templates_python.txt

@@ -890 +890 @@
 
 Thus, to define a custom template tag, you specify how the raw template tag is
 converted into a ``Node`` (the compilation function), and what the node's
-``render()`` method does.
+``render()`` method does. In many cases you can alternatively use the
+``simple_tag`` and ``inclusion_tag`` shortcuts which do the argument parsing
+and variables resolution for you, automatically.
 
 Writing the compilation function
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -1251 +1253 @@
 making it a pain for template authors to pass in all the arguments and remember
 their order. To solve this, Django provides a ``takes_context`` option for
 inclusion tags. If you specify ``takes_context`` in creating a template tag,
-the tag will have no required arguments, and the underlying Python function
-will have one argument -- the template context as of when the tag was called.
+the tag will have no required arguments, and the underlying Python function's
+first argument will be the template context as of when the tag was called.
+Of course, you can still have additional arguments.
 
 For example, say you're writing an inclusion tag that will always be used in a
 context that contains ``home_link`` and ``home_title`` variables that point