From 03fd1cc81c02a5462aeb4dbce0bfe8a2afdef43d Mon Sep 17 00:00:00 2001
From: Aymeric Augustin
Date: Sun, 24 Nov 2013 11:38:43 +0100
Subject: Remove HIDE_DJANGO_SQL configuration option.

It was badly named and HIDE_IN_STACKTRACES provides a more general
solution.

The ability to show code in django.contrib but not in django doesn't
seem particularly useful.

Fix #474.
---
 docs/configuration.rst | 15 +++------------
 1 file changed, 3 insertions(+), 12 deletions(-)

(limited to 'docs')

diff --git a/docs/configuration.rst b/docs/configuration.rst
index eebb6e9..a276aa3 100644
--- a/docs/configuration.rst
+++ b/docs/configuration.rst
@@ -117,20 +117,11 @@ Panel options
   calls. Enabling stacktraces can increase the CPU time used when executing
   queries.
 
-* ``HIDE_DJANGO_SQL``
-
-  Default: ``True``
-
-  Panels: cache, SQL
-
-  If set to ``True`` then code in Django itself won't be shown in
-  stacktraces.
-
 * ``HIDE_IN_STACKTRACES``
 
-  Default: ``('socketserver', 'threading', 'wsgiref', 'debug_toolbar')``. The
-  first value is ``socketserver`` on Python 3 and ``SocketServer`` on Python
-  2.
+  Default: ``('socketserver', 'threading', 'wsgiref', 'debug_toolbar',
+  'django')``. The first value is ``socketserver`` on Python 3 and
+  ``SocketServer`` on Python 2.
 
   Panels: cache, SQL
 
-- 
cgit v1.2.3