Changes between Version 263 and Version 264 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
09/10/2008 01:00:09 AM (6 years ago)
Author:
adrian
Comment:

Fixed formatting and wording.

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v263 v264  
    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.***
     3This 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.'''
    44
    55This 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.
    66
    7 For *future* backwards-incompatible changes -- that is, features that will be removed in version 2.0 -- see the FutureBackwardsIncompatibleChanges page.
     7For *future* backwards-incompatible changes -- that is, features that will be changed or removed in version 2.0 -- see the FutureBackwardsIncompatibleChanges page.
    88
    99[[TOC(inline, depth=1)]]
     
    9696}}}
    9797should be modified to read:
    98 {{{
     98
     99{{{
     100
    99101#!python
    100102c = Client()
     
    130132== Test client removed special casing for file uploads ==
    131133
    132 Before [5465], Django's client in the testing infrastructure had  special casing for file uploads that matched the implementation of the !FileField datatype, making it simpler to use for this case.  To allow for different methods of uploading files (e.g. newforms and oldforms), this has been removed--you will have to update your tests if you depended on this behaviour (look at the HTML source to work out what the field names for posted data should be).
     134Before [5465], Django's client in the testing infrastructure had  special casing for file uploads that matched the implementation of the !FileField datatype, making it simpler to use for this case.  To allow for different methods of uploading files (e.g. newforms and oldforms), this has been removed--you will have to update your tests if you depended on this behavior (look at the HTML source to work out what the field names for posted data should be).
    133135
    134136== Renamed !FloatField to !DecimalField ==
Back to Top