Permalink
Browse files

Documented the backwards incompatibility caused by `in` being a new k…

…eyword in the `if` template tag.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12208 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
spookylukey committed Jan 12, 2010
1 parent c56beed commit d83769f8dcc821a62bcd4f2e6092c2898e0e2b1a
Showing with 2 additions and 1 deletion.
  1. +2 −1 docs/releases/1.2.txt
View
@@ -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``
--------------

0 comments on commit d83769f

Please sign in to comment.