Changes between Version 103 and Version 104 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Jul 6, 2007, 2:08:47 AM (17 years ago)
Author:
Malcolm Tredinnick
Comment:

Added a note about Unicode merge for people previously using non-ASCII data

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v103 v104  
    2727 * May 20, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RenamedFloatFieldtoDecimalField Renamed FloatField to DecimalField]
    2828 * June 22, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Urlpatternsnowcached Urlpatterns now cached]
     29 * July 4, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Unicodemerge Unicode merge]
    2930
    3031== Database constraint names changed ==
    … …  
    227228
    228229If 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.
     230
     231== Unicode merge ==
     232
     233In [5609], the UnicodeBranch was merged into trunk. For any installations using ASCII data, this is fully backwards compatible.
     234
     235If 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.
Back to Top