#24994: Document/check that settings.SECRET_KEY should be a valid unicode string
-------------------------------------+-------------------------------------
Reporter: Baptiste Mispelon | Owner: MaartenPI
Type: | Status: new
Cleanup/optimization |
Component: Core (System | Version: 1.8
checks) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I noticed that #19980 came to the conclusion that `SECRET_KEY` could or
should be bytes. That ticket fixed `Signer` if `SECRET_KEY` is non-ASCII
bytes which is what the proposed check disallows (or warns against) here.
I started a [https://groups.google.com/d/topic/django-
developers/SOKz1e3TTcg/discussion django-developers discussion] to try to
come to some conclusion.
--
Ticket URL: <https://code.djangoproject.com/ticket/24994#comment:15>
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.48f769755dd0e03d97d017c9886a576d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
