I wanted to use as a testbed for (a) learning python (b) using the web application framework.

I was worried it might take a lot of effort to learn a new language, a framework, and a different style of web programming (fastCGI) all at the same time. One of those "Bite off more than you can chew, and then chew like hell." things.

Happily, the chewing was good. gets a nice upgrade. Python is found to be fun to code in. gets a lot of credit for being a powerful tool in a small package.

Some numbers:

The old perl version The new python version:

What's good about

What's good about fastCGI

A couple thoughts on frameworks

One reason people use frameworks is that you "get things for free". For instance, in you get automatic input validation "for free."

But ha ha, it's not really free. The price you pay for free things is needing to comprehend them. The more things a framework gives "for free," the greater the burden on the developer to understand how the free things work and interact.

Python code example:

try: new_tags_string = web.input('tags').tags
except KeyError: 
  response.success = False
  response.messages.append('Error! No tag supplied!')
  print response.write_js()

Someone new to might wonder about "web.input('tags').tags" Seems redundant, right? Well, it's an abbreviation of:

inp = web.input('tags')  # maps user-supplied data to input object, 'tags' parameter is required.
new_tags_string = inp.tags  # get the value of the supplied tags parameter

Make sense? Those two references to 'tags' aren't redundant. The first is an argument to web.input, saying "throw an exception if this parameter isn't found". The second gets the actual parameter value.

Good frameworks make the free things intuitive or easy to learn.'s documentation is pretty bare-bones, but it's good. It doesn't hurt that is small enough to make checking the source code relatively low effort.

That's all, thanks for reading!

Part 2:redesigning the interface.

questions, comments, suggestions.