On 15 sept. 2013, at 20:07, Michael Manfre <[email protected]> wrote: > No amount of code or docs will fix all of the stupid things people do. > Of course, but that isn't a sufficient reason for disabling the security checks. The point of django-secure is to help users with limited knowledge of security best practices. That includes people using runserver in prod.
I'm not sure if you were making a counter-argument or just a tangential comment. Regardless, DEBUG is the canonical way to distinguish dev from prod in Django. Code based on another assumption won't be committed. There's a long term goal to have a more versatile concept of "environment" but that's another discussion. If you want to have that discussion now, please move it to another thread :) -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
