#31757: Adjust default SECRET_KEY to use `dj::insecure` prefix and add matching
deployment system check.
--------------------------------------+------------------------------------
Reporter: Carlton Gibson | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | Version: master
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 felixxm):
* cc: Shai Berger (added)
Comment:
Replying to [comment:2 René Fleschenberg]:
> Shai Berger suggested an alternative approach: Marking the string as
insecure by making it an instance of a custom str subclass
(https://groups.google.com/d/msg/django-developers/CIPgeTetYpk/3a0lkAu-
BgAJ). I am not sure which of the two approaches we prefer.
Prefix is fine, IMO.
--
Ticket URL: <https://code.djangoproject.com/ticket/31757#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.8bbadd1b897dddc7d6f327cfc3eef864%40djangoproject.com.
