Python Web Framework Deathmatch

| Comments

I recently caved and got a 60 day trial Webfaction account, on the advice of Mike Pirnat (be sure to use this url if you sign up so Mike gets a taste).

I was happy right away because Webfaction gives you all the python-y goodness other shared hosts neglect. Things like shell access, easy_install, and a ton of prefab application deployments.

Being a web-framework junkie, I started salivating at my options: Rails, Pylons, Drupal. Hell, they’ve even got Plone. I didn’t think anyone outside the EU ran Plone, but they’ve got it.

Back in my Java days (a story for another day) I worked with older-school platforms like Struts and Spring, and I’ve built a couple of things more recently using Rails.

Being a recent convert to Python in my professional life, I’m eager to see what sweetness Python offers in the framework world.

But all things in moderation. I’ve decided to pick Django, Pylons, and TurboGears to compare. I’ll build a very basic a job board with each, and keep notes on my innermost thoughts and feelings as I do so.

Please keep in mind that I’m coming at this from a pragmatic-purist standpoint. I like beautiful, but I like practical AND beautiful even better.

To keep things in perspective, here are the ground rules:

  1. The app has 3 main ‘pages’: job list, job details, create a job
  2. There is an admin section for the site owner to manage data.
  3. The job list is statically published.
  4. An RSS feed for recent job postings.

First up is Django. Watch this space for the gory details of round 1!

blog comments powered by Disqus