/Disclaimer: I don't know much about FCGI. I've never used it and I don't plan to. Please forgive me if I say something stupid./
For 4,5 years (August 2008 to March 2013), we've had a silly bug in Django that was a workaround for a bug in flup, and to this day no one can say if the original bug in flup is fixed or not. By fixing the bug in Django I've probably re-introduced the bug for users of flup. See https://code.djangoproject.com/ticket/17550. I can't tell if that was the right choice. I hope no one will complain. That wasn't a good experience and I don't plan to spend (read: waste) any more time on bugs related to FCGI. On 15 juil. 2013, at 09:38, Some Developer <[email protected]> wrote: > If the only real concern is that flup is unmaintained and there have been > attempts to contact the original author with no response or no interest then > I am sure all interested parties could work something out between them even > if it is just a fork purely for bug fixes and nothing more. In practice who are the interested parties? - flup's developers have disappeared; - Django's core developers don't use FCGI — at least, I don't know any active core dev who does. That makes FCGI a dead end. At some point we'll have to pull the plug. Right now seems early. With the rise of hosting platforms dedicated to "modern" frameworks and applications — where "modern" means less than 10 years old, which is a long time in today's tech world — I hope cheap WSGI hosting will become a reality, and then we'll have decent arguments for dropping official support for FCGI. An alternative is to leave it up to the community to provide and maintain a FCGI to WSGI adapter. However, writing a robust adapter sounds hard. I'm not sure this plan would work. -- 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.
