On Mon, Jul 22, 2013 at 12:21 PM, Some Developer <someukdevelo...@gmail.com>wrote:
> On 14/07/13 20:17, Florian Apolloner wrote: > >> Hi, >> >> I'd like to get rid of everything FCGI-specific in Django sooner or >> later (rather sooner). Flup isn't maintained since a long time and there >> is no ticket tracker to report stuff. Graham pointed out that if someone >> wants to use FCGI they can use >> http://uwsgi-docs.readthedocs.**org/en/latest/Options.html#** >> fastcgi-socket<http://uwsgi-docs.readthedocs.org/en/latest/Options.html#fastcgi-socket> >> which doesn't even require flup, which sounds like a good compromise to >> me. I'd need some help for the docs from some uWSGI users, since I have >> no idea about it ;) >> >> Thoughts, objections? >> >> Cheers, >> Florian >> > > So has this decision been made yet? If it has myself and others can start > coming up with solutions for those who want FastCGI. If it hasen't then we > can avoid wasting time on something that is going to be a non-issue. > > The sooner that work is started before 1.7 though means that it might not > actually be a problem for users since FastCGI will still work. 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 %-) -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
