summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2018-05-26 20:58:41 -0400
committerTim Graham <timograham@gmail.com>2018-05-26 21:06:58 -0400
commit5cc81cd9eb69f5f7a711412c02039b435c393135 (patch)
treef4416867c5d1510df3117c9ebf22a6a8c64edbf5 /docs
parentb4fd9b5ad481c446636befa40cce5a2b5e9799fc (diff)
Reverted "Fixed #29324 -- Made Settings raise ImproperlyConfigured if SECRET_KEY is accessed and not set."
This reverts commit b3cffde5559c4fa97625512d7ec41a674be26076 due to a regression and performance concerns.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/settings.txt10
1 files changed, 2 insertions, 8 deletions
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index de2651aa82..d6ec76e3f7 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -2066,7 +2066,7 @@ object. See :ref:`how-django-processes-a-request` for details.
``SECRET_KEY``
--------------
-Default: Not defined
+Default: ``''`` (Empty string)
A secret key for a particular Django installation. This is used to provide
:doc:`cryptographic signing </topics/signing>`, and should be set to a unique,
@@ -2079,9 +2079,7 @@ Uses of the key shouldn't assume that it's text or bytes. Every use should go
through :func:`~django.utils.encoding.force_text` or
:func:`~django.utils.encoding.force_bytes` to convert it to the desired type.
-Django will refuse to start if :setting:`SECRET_KEY` is set to an empty value.
-:class:`~django.core.exceptions.ImproperlyConfigured` is raised if
-``SECRET_KEY`` is accessed but not set.
+Django will refuse to start if :setting:`SECRET_KEY` is not set.
.. warning::
@@ -2114,10 +2112,6 @@ affect them.
startproject <startproject>` creates a unique ``SECRET_KEY`` for
convenience.
-.. versionchanged:: 2.1
-
- In older versions, ``SECRET_KEY`` defaults to an empty string.
-
.. setting:: SECURE_BROWSER_XSS_FILTER
``SECURE_BROWSER_XSS_FILTER``