Author: lukeplant
Date: 2010-01-12 07:14:32 -0600 (Tue, 12 Jan 2010)
New Revision: 12208
Modified:
django/trunk/docs/releases/1.2.txt
Log:
Documented the backwards incompatibility caused by `in` being a new keyword in
the `if` template tag.
Modified: django/trunk/docs/releases/1.2.txt
===================================================================
--- django/trunk/docs/releases/1.2.txt 2010-01-12 02:41:57 UTC (rev 12207)
+++ django/trunk/docs/releases/1.2.txt 2010-01-12 13:14:32 UTC (rev 12208)
@@ -49,7 +49,8 @@
'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``
--------------
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
