|
On 27/06/14 03:43, James Bennett wrote:
"FastCGI support via the runfcgi management command will be removed in Django 1.9. Please deploy your project using WSGI." Why does the documentation *persist* in confusing FastCGI with WSGI? FastCGI is a protocol and WSGI is an API. One can deploy a WSGI application over FastCGI and that is exactly what a FastCGI-to-WSGI adapter like flup does (flup is what runfcgi is written for). There are so many clarifications about this out there, including at least one by the author of mod_wsgi (http://stackoverflow.com/questions/1747266/is-there-a-speed-difference-between-wsgi-and-fcgi) And it seems that the point made in the developer thread about deprecation being unwise was simply ignored and intentionally misunderstood (https://groups.google.com/forum/#!topic/django-developers/oGmD8LvLTPg "Deprecate FCGI support in Django 1.7"). My case is just one example - there's an apache/mod_python/python2 application that I can't touch, so to run something on apache with python3 I need mod_fastcgi/mod_fcgi and flup. Mixing mod_python/python2 with mod_wsgi/python3 doesn't work even in daemon mode. -- You received this message because you are subscribed to the Google Groups "Django users" 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-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/53AD2757.5050303%40gmail.com. For more options, visit https://groups.google.com/d/optout. |
- [ANNOUNCE] Django 1.7 release candidate 1 James Bennett
- Re: [ANNOUNCE] Django 1.7 release candidate 1 cercatrova2
- Re: [ANNOUNCE] Django 1.7 release candidate 1 James Bennett
- Re: [ANNOUNCE] Django 1.7 release candidate 1 cercatrova2
