Changes between Version 136 and Version 137 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Dec 2, 2007, 9:31:53 AM (17 years ago)
Author:
Malcolm Tredinnick
Comment:

Documented settings exception changes.

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v136 v137  
    4545 * [6671] Nov. 15, 2007: [#Auto-escapingintemplates Auto-escaping in templates]
    4646 * [6796] Dec 1, 2007: [#Removedunusedsessionbackendfunctions Removed unused session backend functions]
    47 
     47 * [6832] Dec 2, 2007: [#Settingsexceptiontypeschanged Settings exception types changed]
    4848
    4949== Database constraint names changed ==
    … …  
    476476
    477477In [6796] a couple of session backend functions that are no longer needed were removed. In the unlikely event your code was using {{{get_new_session_key()}}} or {{{get_new_session_object()}}}, you will need to switch to using {{{SessionBase._get_new_session_key()}}}.
     478
     479== Settings exception types changed ==
     480
     481In [6382] we changed the possible exceptions raised when initialising Django's settings in order not to interfere with Python's {{{help()}}} function. If there is a problem such as not being able to find the settings module (via the {{{DJANGO_SETTINGS_MODULE}}} environment variable, for example), an `ImportError` is now raised (previously it was `EnvironmentError`). If you try to reconfigure settings after having already used them, a `RuntimeError` is raised (rather than the previous `EnvironmentError`).
Back to Top