#29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not
initialization
--------------------------------------+------------------------------------
Reporter: Jon Dufresne | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Core (Other) | Version: 2.1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"5cc81cd9eb69f5f7a711412c02039b435c393135" 5cc81cd9]:
{{{
#!CommitTicketReference repository=""
revision="5cc81cd9eb69f5f7a711412c02039b435c393135"
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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29324#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.1b1a40318a221fed1380440ba3c8b5e8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
