Django 1.3 compatibility fix - no 'insecure' parameter in Django 1.3 version
Review Request #2236 — Created April 5, 2011 and discarded
Fix error with ReviewBoard passing 'insecure' option to development web-server causing error: serve() got an unexpected keyword argument 'insecure'
Actually, insecure was only for Django 1.3 betas. They've since changed the model. So really, we don't actually want to set this flag anymore, regardless. I think we need something new for 1.3 and devel servers. Looking into it.