Hi, There is a problem in 1.4rc2 where a missing SECRET_KEY causes Django to refuse to start.
According to the current version of the release notes on the website: *In Django 1.4, starting Django with an empty SECRET_KEY will raise a DeprecationWarning. In Django 1.5, it will raise an exception and Django will refuse to start.* * * This doesn't make sense... It currently raises DeprecationWarning which is an exception which causes Django to fail to start. To trigger a deprecation warning while allowing execution to continue you need to use warnings.warn(). As things stand you are essentially implementing the behaviour for both 1.4 *and* 1.5! Cheers, Nick -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/lYpYVlaGlZYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
