Changes between Version 129 and Version 130 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Nov 3, 2007, 10:27:19 AM (17 years ago)
Author:
Luke Plant
Comment:

Added info about r5465 - removed special casing for file uploads in test client

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v129 v130  
    2626 * [5237] May 14, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Newforms:clean_datachangedtocleaned_data Newforms: clean_data changed to cleaned_data]
    2727 * [5302] May 20, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RenamedFloatFieldtoDecimalField Renamed FloatField to DecimalField]
     28 * [5465] June 11, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#TestClientRemovedFileUploadSpecialCasing Test client removed special casing for file uploads]
    2829 * [5516] June 22, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Urlpatternsnowcached Urlpatterns now cached]
    2930 * [5609] July 4, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Unicodemerge Unicode merge]
    … …  
    193194
    194195You will need to do a search-and-replace in your form code and replace clean_data with cleaned_data everywhere.
     196
     197== Test client removed special casing for file uploads ==
     198
     199Before [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).
    195200
    196201== Renamed !FloatField to !DecimalField ==
Back to Top