Code

Changes between Version 100 and Version 101 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
06/22/07 22:50:11 (7 years ago)
Author:
mtredinnick
Comment:

urlpatterns are now cached for performance.

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v100 v101  
    2727 * May 20, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RenamedFloatFieldtoDecimalField Renamed FloatField to DecimalField] 
    2828 * June 17, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#NodeListsmustcontainNodes NodeLists must contain Nodes] 
     29 * June 22, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Urlpatternsnowcached Urlpatterns now cached] 
    2930 
    3031== Database constraint names changed == 
     
    229230 
    230231This 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. 
     232 
     233== Urlpatterns now caches == 
     234 
     235In [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. 
     236 
     237If 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.