diff options
| author | Florian Apolloner <apollo13@users.noreply.github.com> | 2020-07-29 09:06:54 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-29 09:06:54 +0200 |
| commit | 948a874425e7d999950a8fa3b6598d9e34a4b861 (patch) | |
| tree | be16c39b7ab501df06d55d0770b02f120d51b6b8 /docs | |
| parent | 9c9a3fe1180fc92fbd4c3302dbe0b3e083bf0381 (diff) | |
Fixed #29324 -- Made SECRET_KEY validation lazy (on first access).
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/3.2.txt | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/docs/releases/3.2.txt b/docs/releases/3.2.txt index 225f3855f3..fe4b309cb5 100644 --- a/docs/releases/3.2.txt +++ b/docs/releases/3.2.txt @@ -272,7 +272,13 @@ Requests and Responses Security ~~~~~~~~ -* ... +* The :setting:`SECRET_KEY` setting is now checked for a valid value upon first + access, rather than when settings are first loaded. This enables running + management commands that do not rely on the ``SECRET_KEY`` without needing to + provide a value. As a consequence of this, calling + :func:`~django.conf.settings.configure` without providing a valid + ``SECRET_KEY``, and then going on to access ``settings.SECRET_KEY`` will now + raise an :exc:`~django.core.exceptions.ImproperlyConfigured` exception. Serialization ~~~~~~~~~~~~~ |