> To anyone else reading this thread who is still wanting FastCGI I am willing > to help with a third party solution if something is going to come together. > Based on the normal Django release cycle I'd expect 1.7 to be out in either > Q4 this year or Q1 next year so something needs to be done by then > (preferably including testing in production - something which I can help > with).
FastCGI will be pending deprecation in Django 1.7 and deprecated in Django 1.8. It wont' be removed until Django 1.9. You actually need a solution by 2015! > P.S What's a BDFL? :) It's an acronym for "Benevolent Dictator for Life". See https://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life for details. -- 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.
