OMG Django!

When I was in Chicago a while back, I tried explaining the old httpy to Ian Bicking. His response: "Why don't you just use WSGI?" He was right.

Last year at PyCon, I pigeon-holed Guido and forced him to tell me why raising all HTTP Responses was in fact a bad idea. He was *ahem* right.

Also at PyCon, I found myself slinging lots of bullsh-t to a table full of smart people. Ben Collins-Sussman listened patiently, and then interjected, "You should really check out Django."

Folks, you'd think I'd learn. Today it is my pleasure to announce to you all that Django is, in fact, the bee's knees.

I've grown more comfortable with Django lately in helping some folks get it working with Aspen. Tonight I looked at actually migrating a site to Django. It went extremely well. I was afraid it'd be too hegemonic, but in fact it fits perfectly in a hybrid scheme: some files published from the filesystem, some URLs handled by Django. I was able to add just the admin piece, for a single database table that needed an interface. This is huge, because we still manage some content in WordPress! Instead of a risky whole-sale migration, we benefit immediately, and can rescue other parts of the site from PHP at our own pace.

Thank you Django, and thank you Ben! Feed back to Chad Whitacre.