Changes between Version 102 and Version 103 of BackwardsIncompatibleChanges

Timestamp:

Jun 24, 2007, 9:40:28 PM (17 years ago)

Author:

Malcolm Tredinnick

Comment:

Removed reference to a feature that has been backed out.

BackwardsIncompatibleChanges

@@ -26 +26 @@
  * May 14, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Newforms:clean_datachangedtocleaned_data Newforms: clean_data changed to cleaned_data]
  * May 20, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RenamedFloatFieldtoDecimalField Renamed FloatField to DecimalField]
- * June 17, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#NodeListsmustcontainNodes NodeLists must contain Nodes]
  * June 22, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Urlpatternsnowcached Urlpatterns now cached]
 
@@ -223 +222 @@
 If something goes wrong in the above process, just copy your backed up database file over the top of the original file and start again.
 
-== !NodeLists must contain Nodes ==
-
-Django's template rendering classes includes a !NodeList class, which is a subclass of Python's list type. Previously, a !NodeList could hold objects with a {{{render()}}} method (usually Node subclasses) or strings.
-
-In [5482], as part of an optimisation to improve template rendering speeds, this was changed so that every object in a !NodeList must be a !Node subclass (or have the same interface). Strings are no longer allowed.
-
-This change is unlikely to affect most code. However, if you have a custom template tag that uses !NodeList and does not populate it with Nodes, you should change your code to use normal lists instead. Django's own !ForNode class (for implementing "for loops" in templates) was the only internal code affected by this change. Consult the current implementation of {{{ForNode.iter_render}}} to see how the !NodeList usage has been replaced.
-
 == Urlpatterns now cached ==