diff options
| author | Luke Plant <L.Plant.98@cantab.net> | 2010-01-12 13:14:32 +0000 |
|---|---|---|
| committer | Luke Plant <L.Plant.98@cantab.net> | 2010-01-12 13:14:32 +0000 |
| commit | d83769f8dcc821a62bcd4f2e6092c2898e0e2b1a (patch) | |
| tree | da71fffcd2e63c6a26201a6d538f49004a9cd80a /docs | |
| parent | c56beed24061bf94b67be21806fa654a1e180b5f (diff) | |
Documented the backwards incompatibility caused by `in` being a new keyword in the `if` template tag.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@12208 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.2.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/releases/1.2.txt b/docs/releases/1.2.txt index 6d8a4dc0cd..197900f3b6 100644 --- a/docs/releases/1.2.txt +++ b/docs/releases/1.2.txt @@ -49,7 +49,8 @@ Due to new features in the :ttag:`if` template tag, it no longer accepts 'and', 'or' and 'not' as valid **variable** names. Previously, that worked in some cases even though these strings were normally treated as keywords. Now, the keyword status is always enforced, and template code such as ``{% if not %}`` or -``{% if and %}`` will throw a ``TemplateSyntaxError``. +``{% if and %}`` will throw a ``TemplateSyntaxError``. Also, ``in`` is a new +keyword and so is not a valid variable name in this context. ``LazyObject`` -------------- |