Changes between Version 139 and Version 140 of BackwardsIncompatibleChanges

Timestamp:

Dec 4, 2007, 2:12:12 AM (17 years ago)

Author:

anonymous

Comment:

initialising -> initializing

BackwardsIncompatibleChanges

@@ -480 +480 @@
 == Settings exception types changed ==
 
-In [6832] 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`). See #5743 for the details of this change.
+In [6832] we changed the possible exceptions raised when initializing 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`). See #5743 for the details of this change.
 
 == Generic views' empty defaults ==