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
This commit is contained in:
parent
c56beed240
commit
d83769f8dc
|
@ -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``
|
||||
--------------
|
||||
|
|
Loading…
Reference in New Issue