On 15 juil. 2013, at 14:13, mjl Martin J. Laubach <[email protected]> wrote:
> Is there actually a problem with flup? Yes, there are. About a hundred tickets related to fastcgi or flup were reported in the history of Django: https://code.djangoproject.com/search?q=flup&ticket=on https://code.djangoproject.com/search?q=fastcgi&ticket=on https://code.djangoproject.com/search?q=runfcgi&ticket=on Even though the flow of new tickets has died off since 2010, several tickets are still open: https://code.djangoproject.com/ticket/9191 https://code.djangoproject.com/ticket/10464 https://code.djangoproject.com/ticket/11694 https://code.djangoproject.com/ticket/11754 https://code.djangoproject.com/ticket/12322 https://code.djangoproject.com/ticket/12464 https://code.djangoproject.com/ticket/13603 https://code.djangoproject.com/ticket/14958 https://code.djangoproject.com/ticket/17081 https://code.djangoproject.com/ticket/20751 (Some look easy but haven't received much love.) Besides bugs, support for deployment techniques other than WSGI accounts for significant complexity in the core request handling. The situation has improved since we dropped support for mod_python, but the code isn't in very good shape overall, and I find it hard to work in this area. -- 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.
