From Raw WSGI to a framework

While useful for unterstanding how WSGI works, the examples shown until now are still far being called a framework. A Python webframework usually has the following attributes:

  1. It pre-process the environment and yields some request object for the programmer to work with. This request is sometimes injected to the callable we program, as for example in Pyramid:
# First view, available at http://localhost:6543/
def home(request):
    return Response('<body>Visit <a href="/howdy">hello</a></body>')

# /howdy
def hello(request):
    return Response('<body>Go back <a href="/">home</a></body>')

or in Django:

from django.http import HttpResponse

def index(request):
    return HttpResponse("Hello, world. You're at the polls index.")

In other cases it is a global instace object you have to explicitly import and make use of, as in the case of Flask or Bottle:

from flask import request

@app.route('/login', methods=['GET', 'POST'])
def login():
    if request.method == 'POST':
  1. Add a Response wrapper, which makes it easier to write correct responses. As such, we don’t have manually call start_response every time. Nor do we remember that our return value is some kind of iterable. Here is an example from Flask:

    def index():
       response = Response("Unicorns are OK")
       response.headers['X-Parachutes'] = 'parachutes are cool'
       response.set_cookie('username', 'the username')
       return response
  2. Add some smart way of handling URL and request query paramters. For example Django injects URL parameter to your application logic, which allowes you to make explicit use of them:

    # in
    def detail(request, question_id):
      return HttpResponse("You're looking at question %s." % question_id)
    # in
    from . import views
    urlpatterns = [
    # ex: /polls/
    url(r'^$', views.index, name='index'),
    # ex: /polls/5/
    url(r'^(?P<question_id>[0-9]+)/$', views.detail, name='detail'),
Forms are processed and saved into a Dictionary like object, request.POST and query data in saved into a request.GET.
  1. Add session and cookie management such that you manage some state. Using cookies you can store information in the browser, for example login cookie. And using sessions you can remember how the user interacted with your website, for example you can remeber the login date and time.
  2. Optionally, add HTML templating.
  3. Optionally, add some persistency layer, e.g ORM or a NoSQL abstraction layer.

Alas, we are not going to implement all those in just a couple of hours. Instead, we are going to see how we can exploit Python’s data model to build convinient Python APIs for out Nano Python framwork. We start by implementing dictionary like session storage.