From 62bdb6eae8e62e7390f26daa261f75e5cca3b8e7 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Tue, 11 Mar 2008 03:15:07 +0000 Subject: queryset-refactor: Merged from trunk up to [7216]. git-svn-id: http://code.djangoproject.com/svn/django/branches/queryset-refactor@7219 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/templates_python.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'docs/templates_python.txt') diff --git a/docs/templates_python.txt b/docs/templates_python.txt index c6e9223e9f..43ef016ed4 100644 --- a/docs/templates_python.txt +++ b/docs/templates_python.txt @@ -629,9 +629,10 @@ the given Python module name, not the name of the app. Once you've created that Python module, you'll just have to write a bit of Python code, depending on whether you're writing filters or tags. -To be a valid tag library, the module contain a module-level variable named -``register`` that is a ``template.Library`` instance, in which all the tags and -filters are registered. So, near the top of your module, put the following:: +To be a valid tag library, the module must contain a module-level variable +named ``register`` that is a ``template.Library`` instance, in which all the +tags and filters are registered. So, near the top of your module, put the +following:: from django import template @@ -983,7 +984,7 @@ Notes: exception. It should fail silently, just as template filters should. Ultimately, this decoupling of compilation and rendering results in an -efficient template system, because a template can render multiple context +efficient template system, because a template can render multiple contexts without having to be parsed multiple times. Auto-escaping considerations -- cgit v1.3