Changes between Version 263 and Version 264 of BackwardsIncompatibleChanges

Timestamp:

Sep 10, 2008, 1:00:09 AM (16 years ago)

Author:

Adrian Holovaty

Comment:

Fixed formatting and wording.

BackwardsIncompatibleChanges

@@ -1 +1 @@
 = Backwards-incompatible changes =
 
-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.***
+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.'''
 
 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.
 
-For *future* backwards-incompatible changes -- that is, features that will be removed in version 2.0 -- see the FutureBackwardsIncompatibleChanges page.
+For *future* backwards-incompatible changes -- that is, features that will be changed or removed in version 2.0 -- see the FutureBackwardsIncompatibleChanges page.
 
 [[TOC(inline, depth=1)]]
@@ -96 +96 @@
 }}}
 should be modified to read:
-{{{
+
+{{{
+
 #!python
 c = Client()
@@ -130 +132 @@
 == Test client removed special casing for file uploads ==
 
-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).
+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 behavior (look at the HTML source to work out what the field names for posted data should be).
 
 == Renamed !FloatField to !DecimalField ==