Changes between Version 100 and Version 101 of BackwardsIncompatibleChanges

Timestamp:

Jun 23, 2007, 12:50:11 AM (17 years ago)

Author:

Malcolm Tredinnick

Comment:

urlpatterns are now cached for performance.

BackwardsIncompatibleChanges

@@ -27 +27 @@
  * 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]
 
 == Database constraint names changed ==
@@ -229 +230 @@
 
 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 caches ==
+
+In [5516] a speed improvement was made for reverse URL lookups, particularly. Part of this involved caching information that was unlikely to change: the {{{urlpatterns()}}} contents.
+
+If you were somehow relying on the fact that you could change your {{{urls.py}}} files and not have to restart Django, you can no longer do that. Edits require a restart.