E-Scribe : a programmer’s blog

About Me

PBX I'm Paul Bissex. I build web applications using open source software, especially Django. Started my career doing graphic design for newspapers and magazines in the '90s. Then wrote tech commentary and reviews for Wired, Salon, Chicago Tribune, and others you never heard of. Then I built operations software at a photography school. Then I helped big media serve 40 million pages a day. Then I worked on a translation services API doing millions of dollars of business. Now I'm building the core platform of a global startup accelerator. Feel free to email me.

Book

I co-wrote "Python Web Development with Django". It was the first book to cover the long-awaited Django 1.0. Published by Addison-Wesley and still in print!

Colophon

Built using Django, served with gunicorn and nginx. The database is SQLite. Hosted on a FreeBSD VPS at Johncompanies.com. Comment-spam protection by Akismet.

Pile o'Tags

Stuff I Use

bitbucket, Django, Emacs, FreeBSD, Git, jQuery, LaunchBar, Markdown, Mercurial, OS X, Python, Review Board, S3, SQLite, Sublime Text, Ubuntu Linux

Spam Report

At least 236428 pieces of comment spam killed since 2008, mostly via Akismet.

YAPWF: Aaron Swartz's web.py released

Released today: web.py. (Source, documentation, backstory.)

Even though everybody (including Aaron) refers to this as a framework, it's a lot more library-like than most of the frameworks it's ostensibly competing with -- by design, it seems. It's very compact -- only about 1000 lines of fairly dense Python. (About 275 of those are a template for pretty error pages adapted from Django though.)

Personally, I find the compact, all-in-one style very appealing. Less for a newbie to absorb and less for an experienced user to keep track of. Yes, it does require a template engine and a database wrapper to be useful, but the core is still extremely lean.

I'm very curious to see how web.py grows. Will users demand built-in ORM and support for other databases? Templating alternatives? Form validation? Admin tools and auto-generated CRUD? And as those things get added, will web.py asymptotically approach Turbogears, or Django, or ... ?

It's conventional to sigh and groan when a new Python web app framework is released. I don't know that I'll use web.py for anything beyond the obligatory test run, but I know that Aaron motivated some good little changes in Django while he was wrestling with it and birthing web.py.

In the end I think that whatever small amount of energy dissipation web.py causes will be more than offset by the ideas that it (by which I mean Aaron, really) injects into the discussion of what a web framework should be and do.

Tuesday, January 3rd, 2006
+ +
4 comments

Comment from Adam Hayward , later that day

Sorry for the off topic post, but I really dislike the way you use strikethoughs to denote visited links.

Thanks for the news about web.py!

Comment from Paul , later that day

I really dislike the way you use strikethoughs to denote visited links

Noted -- I may go back to color change instead.

And you're welcome!

Comment from Anonymous , later that day

yeah, nice post ... but damn I hate those strikethrougths too

Comment from Raymond Lutz , 1 day later

Just to point to this YAPWF: spiffy from Wilfredo Sanchez, http://www.wsanchez.net/blog/archives/000091.html

' haven't check it...

Comments are closed for this post. But I welcome questions/comments via email or Twitter.