On Monday, July 15, 2013 7:07:08 AM UTC+2, Russell Keith-Magee wrote: > > I'm not arguing that FastCGI is a good option, just that it's prevalent. > And if we're going to stop supporting it, we need to be aware of who we're > cutting off. >
We won't cut anything off (maybe aside from the runfcgi command). Supporting FCGI should be as easy as shown in the flask docs: http://flask.pocoo.org/docs/deploying/fastcgi/ -- This means that even if we remove everything FCGI specific from Django this doesn't prevent people from using FCGI+Django, it just means they have a bit more work to do (although if you look at the flask docs, it's really just a .fcgi file). Cheers, Florian -- 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.
