Changes between Version 106 and Version 107 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Jul 12, 2007, 12:34:16 AM (17 years ago)
Author:
Adrian Holovaty
Comment:

Added anchor link

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v106 v107  
    2828 * [5516] June 22, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Urlpatternsnowcached Urlpatterns now cached]
    2929 * [5609] July 4, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Unicodemerge Unicode merge]
    30  * [5654] July 12, 2007: Changed __init__() parameters in syndication framework's Feed class
     30 * [5654] July 12, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#ChangedinitparametersinsyndicationframeworksFeedclass Changed {{{__init__()}}} parameters in syndication framework's Feed class]
    3131
    3232== Database constraint names changed ==
    … …  
    236236If you were using non-ASCII data, Django would have behaved unreliably in some cases previously and so backwards-compatibility was neither completely possible nor desirable. However, some people may have been able to get by with non-ASCII data successfully. They might now experience some different errors to previously. Porting code to work correctly with non-ASCII data is fairly simple. Follow [http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist this checklist] for fastest results.
    237237
    238 == Changed __init__() parameters in syndication framework's Feed class ==
     238== Changed {{{__init__()}}} parameters in syndication framework's Feed class ==
    239239
    240240In [5654], we changed the {{{Feed}}} class' {{{__init__()}}} method to take an {{{HttpRequest}}} object as its second parameter, instead of the feed's URL. This allows the syndication framework to work without requiring the sites framework.
Back to Top