Changes between Version 195 and Version 196 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Jul 29, 2008, 7:52:38 AM (16 years ago)
Author:
simon
Comment:

Added [7923] to backwards incompatible changes; it changed some of the ModelAdmin method signatures

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v195 v196  
    6363 * [7844] July 6, 2008 [#Translationtoolsnowpartofdjango-admin.py Translation tools now part of `django-admin.py`]
    6464 * [7859] July 7, 2008 [#Uploadedfilechanges More uploaded file changes].
     65 * [7923] July 14, 2008 [#ChangestoModelAdminsave_addsave_changeandrender_change_formmethodsignatures Changes to ModelAdmin save_add, save_change and render_change_form method signatures].
    6566 * [7949] July 18, 2008 [#MySQL_oldbackendremoved MySQL_old backend removed]
    6667 * [7952] July 18, 2008 [#Genericviewsusenewforms Create/update generic views use newforms]
     
    679680In [7949] we removed the `mysql_old` backend. It was only available for backwards compatibility with a version of `MySQLdb` that was in popular use in some ISPs at the time. Since `MySQLdb-1.2.1p2` was released over 2 years ago and that version, or anything later, works with the `mysql` backend, we have now removed this formerly deprecated backend.
    680681
     682== Changes to !ModelAdmin save_add, save_change and render_change_form method signatures ==
     683
     684[7923] removed some places where model was being passed around for no reason - this will only affect you if you have custom ModelAdmin subclasses that over-ride those methods.
     685
    681686== Generic views use newforms ==
    682687
Back to Top