Changes between Version 136 and Version 137 of BackwardsIncompatibleChanges

Timestamp:

Dec 2, 2007, 9:31:53 AM (16 years ago)

Author:

Malcolm Tredinnick

Comment:

Documented settings exception changes.

BackwardsIncompatibleChanges

@@ -45 +45 @@
  * [6671] Nov. 15, 2007: [#Auto-escapingintemplates Auto-escaping in templates]
  * [6796] Dec 1, 2007: [#Removedunusedsessionbackendfunctions Removed unused session backend functions]
-
+ * [6832] Dec 2, 2007: [#Settingsexceptiontypeschanged Settings exception types changed]
 
 == Database constraint names changed ==
@@ -476 +476 @@
 
 In [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()}}}.
+
+== Settings exception types changed ==
+
+In [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`).