#29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not
initialization
--------------------------------------+------------------------------------
Reporter: Jon Dufresne | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: 2.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* status: closed => new
* has_patch: 1 => 0
* resolution: fixed =>
* severity: Release blocker => Normal
Comment:
I reverted the original patch for now as Claude expressed some concerns,
"I'm not sure to like the additional test for every setting access, for a
corner-case use case. I think we should consider reverting the initial
patch instead."
I'll leave the ticket open for Jon to provide an alternative patch or to
close the ticket as wontfix.
--
Ticket URL: <https://code.djangoproject.com/ticket/29324#comment:10>
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.84aab8357399a89fd4f9bdc02061ec60%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
