  Using the thread-safe Django 1.2 renderer, you will instead get::
  
      even even even even ...
  
  This is because the each rendering of the :ttag:`include` tag is an
  independent rendering. When the :ttag:`cycle` tag was not thread safe,
  the state of the :ttag:`cycle` tag would leak between multiple renderings
  of the same :ttag:`include`. Now that the :ttag:`cycle` tag is thread safe,
  this leakage no longer occurs.
  
 
</s> remove the state of the :ttag:`cycle` tag would leak between multiple renderings
of the same :ttag:`include`. Now that the :ttag:`cycle` tag is thread safe,
this leakage no longer occurs.
 </s> add the state of the :ttag:`cycle` tag would leak between multiple
renderings of the same :ttag:`include`. Now that the :ttag:`cycle` tag
is thread safe, this leakage no longer occurs. </s> remove Using the non thread-safe, pre-Django 1.2 renderer, this would output::
 </s> add Using the non-thread-safe, pre-Django 1.2 renderer, this would output:: </s> remove    requires the use of the csrf_token template tag in the template. If you
 </s> add    requires the use of the ``csrf_token`` template tag in the template. If you </s> remove In previous versions of Django ``BoleanFields`` under MySQL would return their
values as either ``1`` or ``0``, instead of ``True`` or ``False``.  For most
people this shouldn't have been a problem because ``bool`` is a subclass of
``int``, however in Django 1.2 MySQL correctly returns a real ``bool``.  The
only time this should ever be an issue is if you were expecting printing the
 </s> add In previous versions of Django, a model's ``BooleanField`` under MySQL
would return its value as either ``1`` or ``0``, instead of ``True``
or ``False``; for most people this wasn't a problem because ``bool``
is a subclass of ``int`` in Python. In Django 1.2, however,
``BooleanField`` on MySQL correctly returns a real ``bool``.  The only
time this should ever be an issue is if you were expecting the </s> remove  * All of the CSRF has moved from contrib to core (with backwards compatible
   imports in the old locations, which are deprecated).
 </s> add  * All of the CSRF has moved from contrib to core (with backwards
   compatible imports in the old locations, which are deprecated and
   will cease to be supported in Django 1.4).
This is because each rendering of the :ttag:`include` tag is an
  Using the thread-safe Django 1.2 renderer, you will instead get::
  
      even even even even ...
  
This is because each rendering of the :ttag:`include` tag is an
  independent rendering. When the :ttag:`cycle` tag was not thread safe,
  the state of the :ttag:`cycle` tag would leak between multiple renderings
  of the same :ttag:`include`. Now that the :ttag:`cycle` tag is thread safe,
  this leakage no longer occurs.
  
keep keep keep keep replace keep keep keep keep keep
 Update 1.2 release notes in anticipation of final release.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@13259 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/releases/1.2.txt