Code

Changes between Version 268 and Version 269 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
11/14/09 11:22:21 (4 years ago)
Author:
lukeplant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v268 v269  
    11= Backwards-incompatible changes = 
    22 
    3 This section of the Django wiki documents all backwards-incompatible changes to Django over the years. Now that Django has reached version 1.0, its APIs will remain stable until version 2.0. '''If you're already running Django 1.0, you need not worry about anything on this page.''' 
    4  
    5 This page lists all backwards-incompatible changes to Django since the 0.96 release. Django historians, you can view pre-0.96 changes on the OlderBackwardsIncompatibleChanges page. 
    6  
    7 For *future* backwards-incompatible changes -- that is, features that will be changed or removed in version 2.0 -- see the FutureBackwardsIncompatibleChanges page. 
     3This section of the Django wiki documents all backwards-incompatible changes to Django from 0.96 to 1.0. '''If you're already running Django 1.0, you need not worry about anything on this page.'''  Django historians, you can view pre-0.96 changes on the OlderBackwardsIncompatibleChanges page. 
     4 
     5For changes '''after version 1.0''', which are kept to a minimum due to our [http://docs.djangoproject.com/en/dev/misc/api-stability/ API stability policy], including changes in trunk, see the [http://docs.djangoproject.com/en/dev/releases/ release notes] in the official documentation. 
     6 
     7For future changes, see the [http://docs.djangoproject.com/en/dev/internals/deprecation/ Deprecation Timeline] 
    88 
    99[[TOC(inline, depth=1)]]