Changes between Version 67 and Version 68 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Sep 27, 2006, 9:47:59 PM (18 years ago)
Author:
Adrian Holovaty
Comment:

Added "Removed ENABLE_PSYCO setting"

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v67 v68  
    3838 * August 2, 2006: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Databaseconstraintnameschanged Database constraint names changed]
    3939 * August 11, 2006: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Backslashescapingchanged Backslash escaping changed]
     40 * September 27, 2006: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RemovedENABLE_PSYCOsetting Removed ENABLE_PSYCO setting]
    4041
    4142== Moved mod_python handler ==
     
    598599MyModel.objects.filter(text__contains='\\')
    599600}}}
     601
     602== Removed ENABLE_PSYCO setting ==
     603
     604As of [3877], the {{{ENABLE_PSYCO}}} setting no longer exists. If your settings file includes {{{ENABLE_PSYCO}}}, nothing will break per se, but it just won't do anything. If you want to use psyco with Django, write some custom middleware that activates psyco.
Back to Top