#29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not
initialization
-------------------------------------+-------------------------------------
Reporter: Jon Dufresne | Owner: Florian
Type: | Apolloner
Cleanup/optimization | Status: closed
Component: Core (Other) | Version: 2.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"948a874425e7d999950a8fa3b6598d9e34a4b861" 948a8744]:
{{{
#!CommitTicketReference repository=""
revision="948a874425e7d999950a8fa3b6598d9e34a4b861"
Fixed #29324 -- Made SECRET_KEY validation lazy (on first access).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29324#comment:17>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.023deca2145efdb1006b3be8ddbb9309%40djangoproject.com.
