On 22/07/13 05:47, Russell Keith-Magee wrote:
Based on the feedback from this thread (and the fact that multiple core
devs, including a BDFL have weighed in), I think it's safe to say that
the decision has been made. The only question at this point is how long
it takes before someone commits the changeset that implements the start
of the deprecation process.
Yours,
Russ Magee %-)
Thanks. Its always better to know that a definitive decision has been made.
I guess now we can start looking into third party alternatives.
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).
P.S What's a BDFL? :)
--
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.
