On 14.07.2013, at 21:17, Florian Apolloner <f.apollo...@gmail.com> 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 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? If you're suggesting to move the FastCGI code into a separate app: +1 In other words, I don't think we can remove it from Django and not provide a migration path for FastCGI users. It's simple enough to move the runfcgi management command and the flup based handler into a separate app without having to risk changes in behavior. Jannis PS: I've just registered django-fcgi on PyPI in case you want to release it under that name. -- 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.
