<metaname="description" content="Full Stack Python shows how an entire Python web application is built and deployed. Each section of the guide explains a different key concept, from the server through the Python WSGI web framework to the front end JavaScript.">
<p>A <aclass="reference external" href="http://wsgi.readthedocs.org/en/latest/">Web Server Gateway Interface</a>
(WSGI) server implements the web server side of the WSGI interface for
running Python web applications. The WSGI standard v1.0 is specified in
<aclass="reference external" href="http://www.python.org/dev/peps/pep-0333/">PEP 0333</a>. As of September 2010,
WSGI v1.0 is superseded by
<aclass="reference external" href="http://www.python.org/dev/peps/pep-3333/">PEP 3333</a>, which defines the
v1.0.1 WSGI standard.</p>
<imgalt="WSGI Server <-> Web server <-> Browser" class="technical-diagram" src="theme/img/web-browser-server-wsgi.png" style="width: 100%;" />
<p>Requests from the browser that are not for static assets (this is specified
in the web server's configuration which requests are for static assets and
which are not) are passed to the WSGI server. Once the request is
processed and generated by the WSGI server, the response is passed
back through the web server and onto the browser.</p>
<aclass="reference external" href="https://github.com/unbit/uwsgi-docs">uWSGI</a>, and
<aclass="reference external" href="http://www.gevent.org/">gevent</a> are common WSGI server implementations.</p>
<p>This <aclass="reference external" href="http://agiliq.com/blog/2013/07/basics-wsgi/">Basics of WSGI</a> post
contains a simple example of how a WSGI-compatible application works.</p>
<p><aclass="reference external" href="http://www.apreche.net/complete-single-server-django-stack-tutorial/">Complete single server Django stack tutorial</a> is thorough and informative for