Changes between Version 162 and Version 163 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
05/22/2008 02:30:12 PM (7 years ago)
Author:
lukeplant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v162 v163  
    5555 * [7364] March 26, 2008 [#Removedado_mssql Removed ado_mssql]
    5656 * [7477] April 27, 2008 [#Queryset-refactormerge Queryset-refactor merge]
    57  * [7545] May 22, 2008 [#descriptioninAdmin.fieldsnowescaped Description option in Admin.fields now escaped]
     57
    5858== Database constraint names changed ==
    5959
     
    591591== Queryset-refactor merge ==
    592592In [7477] the [QuerysetRefactorBranch queryset-refactor branch] was merged into trunk. This is mostly backwards compatible, but there are a few points to note. Rather than list them here, refer to the [QuerysetRefactorBranch#Backwardsincompatiblechanges backwards incompatible changes] section on the branch's wiki page.
    593 
    594 == `description` in Admin.fields now escaped ==
    595 In [6671], autoescaping in templates meant that the `description` option of the Admin `fields` option was escaped, whereas the [http://www.djangoproject.com/documentation/model-api/#description documentation] stated that it would be included verbatim so that HTML could be used.  Since `django.utils.safestring.mark_safe` can be used for HTML, the documentation was changed in [7545].  If you were using HTML in  description options previously, you need to wrap the string in `mark_safe`.
Back to Top