--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20D8A2BD-BC9C-4F02-9038-044687165DE9%40pelme.se.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20D8A2BD-BC9C-4F02-9038-044687165DE9%40pelme.se.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/A16A11DF-1439-46EF-BF0D-85C483F53608%40pelme.se.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20D8A2BD-BC9C-4F02-9038-044687165DE9%40pelme.se.
Is it going to be easy to adjust the semantics of SECRET_KEY
to support sequences like that? I’d imagine a lot of third party packages that expect SECRET_KEY
to be a string would break in weird ways (thanks to both strings and tuples of strings being iterables that yield strings).
Here’s a quick search on GitHub: https://github.com/search?q=%22settings.SECRET_KEY%22&type=Code
To ease the backward compatibility concerns we could use SECRET_KEYS
, then make SECRET_KEY
(if it is not explicitly defined) map to SECRET_KEYS[0]
? Third party packages using would not necessarily work with the backwards verification but they would at least not break and continue to work as expected.
Tom
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/F62259DE-AA39-40ED-8E13-472CFAB9AFBA%40polytechnique.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2A3BF993-E132-4F93-8C59-1DD49F3EB9F0%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1YGrV3EiN16acGjzDviBJRSsXZwdhSXv1AB0nxyU%3D_oA%40mail.gmail.com.