title: Django: do I need to restart Apache when deploying?
body: <p>I just noted an annoying factor: Django requires either a restart of the server or <a href="http://en.wikipedia.org/wiki/Common_Gateway_Interface" rel="nofollow noreferrer">CGI</a> access to work. The first option is not feasible if you don't have access to the Apache server process. The second, as far as I know, is detrimental to performance, and in general the idea of running a CGI makes me uncomfortable.</p>
  
  <p>I also recently saw a presentation titled "why I hate Django". Although I did not really shared most of the speaker's (a Flickr guy) points, this fact of re-starting the server sounded very annoying.</p>
  
  <p>I would like to know your motivated experience in this regard. Should I continue working with Django and use it as a CGI, or favor another Python framework ? Is the CGI option that bad, and should I be concerned about it, or it's a viable option (for performance and scalability) ?</p>