Changeset 7537

Timestamp:

05/16/08 18:24:36 (2 months ago)

Author:

lukeplant

Message:

Added DEBUG_PROPAGATE_EXCEPTIONS setting that helps testing under e.g. twill

Files:

• django/trunk/django/conf/global_settings.py (modified) (1 diff)
• django/trunk/django/core/handlers/base.py (modified) (1 diff)
• django/trunk/docs/settings.txt (modified) (1 diff)

django/trunk/django/conf/global_settings.py

@@ -12 +12 @@
-DEBUG = False
-TEMPLATE_DEBUG = False
+# True if BaseHandler.get_response() should propagate raw exceptions
+# rather than catching them.  This is useful under some testing siutations,
+# and should never be used on a live site.
+DEBUG_PROPAGATE_EXCEPTIONS = False
-
-# Whether to use the "Etag" header. This saves bandwidth but slows down performance.

django/trunk/django/core/handlers/base.py

@@ -116 +116 @@
-            exc_info = sys.exc_info()
-            receivers = dispatcher.send(signal=signals.got_request_exception, request=request)
-
+
+
+
+
-                from django.views import debug
-                return debug.technical_500_response(request, *exc_info)

django/trunk/docs/settings.txt

@@ -391 +391 @@
-the like all give attackers extra information about your server. Never deploy a
-site with ``DEBUG`` turned on.
+
+DEBUG_PROPAGATE_EXCEPTIONS
+--------------------
+
+Default: ``False``
+
+If set to True, Django's normal exception handling of view functions
+will be suppressed, and exceptions will propagate upwards.  This can
+be useful for some test setups, and should never be used on a live
+site.
-
-DEFAULT_CHARSET