WSGI defines the interface between web services written in Python and HTTP. mod_wsgi is the Apache implementation. FLUP is frequently used to gateway WSGI to Fa

WSGI defines the interface between web services written in Python and HTTP. mod_wsgi is the Apache implementation. FLUP is frequently used to gateway WSGI to FastCGI (for use with nginx). There are others. Until now, people writing WSGI applications (mostly framework authors) have been held back by lack of standardization. WSGI adapters such as mod_wsgi have been tracking PEP 3333 for some time, but web application/framework authors have been reluctant to move forward without standardization. Jacob Kaplan-Moss wrote: "The lack of a WSGI answer on Py3 is the main thing that's keeping me, personally, from feeling excited about the platform. Once that's done I can feel comfortable coding to it -- and browbeating those who don't support it." See http://mail.python.org/pipermail/web-sig/2011-January/004902.html http://mail.python.org/pipermail/web-sig/2011-January/004902... for more of his point of view on why PEP 3333 is important. So: standardization has arrived. I would say that lack of WSGI for Python 3.x was the primary factor holding back widespread standardization on Python 3.x. It will take some time for adoption to occur nonetheless--there are other factors. It is extra work to maintain a project with Python 3.x and 2.x compatibility. Also the Python 3.x standard library needs more users to smooth out the lumps. Nonetheless, this is a big deal and should be celebrated :-)