Pythoneering

It’s that time of the year again, when our final-year students begin their project work. In the run-up to project selection, it was tremendously encouraging to see how many of them were keen on using Python in general, and the Django framework in particular. And it now looks like two or maybe three of my four students will be making significant use of Django. Java doesn’t go unrepresented either, with one student planning on doing interesting things with Eclipse and version control.

Anyway, I hope all of my guys get stuck in and do some good work. Projects that go well can be as rewarding for the supervisor as they are for the student!

Fuzzyman reports that an active member of the IronPython community has released his own version of IronPython, containing various bug fixes and enhancements, because the IronPython team are apparently “unable to accept outside contributions”.

This is disappointing news. Hopefully, Microsoft will be able to sort out a better development model. IronPython is one of the most interesting things they’ve done lately, and it would be a shame if the project failed to build momentum simply because Microsoft couldn’t bring themselves to embrace an inclusive, community-driven approach to software development.

Having only recently decided to get a personal Django-based project off the ground, I now find myself with an opportunity to use Django for a project at work. I think that RunLog is going to have to take a backseat while I concentrate on something a little more serious.

I’ve recently been thinking about why I like Django, and why I’ve ended up spending time with it rather than with something else like TurboGears. It may be largely accidental, in that I came across Django before I’d heard of TurboGears. In fact, my prior experiences with CherryPy lead me to suspect that I’d have been pretty happy with TurboGears, had I discovered it sooner. But Django snared me first.

So why do I stick with Django for my experimentation with web frameworks? Here, in no particular order, is a list of the things it has that I particularly like:

• A well-designed, easily-navigable, unfussy website, providing access to some excellent tutorials and other documentation
• A simple, compact template language that forces business logic into the view code, where it belongs
• A rich set of generic views that allow useful functionality to be delivered with a minimum of code
• An attractive and highly capable administrative interface to the underlying database, generated for free from the data models

All pretty compelling, as far as I’m concerned. I wouldn’t rule out switching to another framework, but it would have to provide all of the above, and improve on some of it, to tempt me away from Django.

Guido’s recent pronouncement recommending Django as ‘the’ Python Web Framework seems to have got some folk hot under the collar, and prompted a few criticisms of Django. I wonder whether Django’s image might suffer a little at the hands of people envious of the endorsement it appears to have received. I hope not.

Hopefully, people will realise that the comments of one individual, even one so illustrious as the BDFL, aren’t a serious threat to a project with the momentum that TurboGears has. But if Guido’s comments have the effect of dissuading Joe Programmer from writing Yet Another Python Web Framework, and encourage him to help make one of the existing successful frameworks even better, then they will have been well made.