For those who hadn’t seen the announcement, the sqlalchemy team has released v0.4 (they don’t believe in big version numbers, do they?). I mentioned previously that they seem to be doing good things, and I’m really looking forward to having another bash at it this time round.
The main thing, though, is that they’ve really put a lot of effort into the docs. They’ve not just added new features; they’ve produced a sort of front page with lots of useful links, and the docs themselves are up to scratch. If I do have a grumble, it’s the same grumble you have with any many-layered software: there’s more than one way to do it, and it’s not clear at first which way you should go.
Great work from the sqlalchemy team!
Michael Bayer, the indefatigable author of Myghty, sqlalchemy and Mako is moving sqlalchemy forward apace. He’s recently proposed what I see as a sensible simplification of the varied query/select methods which sqlalchemy offers. I’ve been following sqlalchemy for a while. The trouble is that I’m first and foremost a SQL developer and first and foremost a Python developer. Trying to marry the two is something I find difficult. If I were a SQL dev who dabbled in Python, I’d just throw SQL statements around and do things with the results. If I were a Pythonista who needed some data, I’d use sqlalchemy (or SQLObject, or whatever) and be happy. Because I’m both I want the best of both worlds. Maybe sqlalchemy’s about to offer it!
In other news, Michael Foord (aka Fuzzyman) has started a wiki for IronPython recipes. It even got a mention on O’Reilly’s Windows DevCenter. (It’s only a shame they can’t spell Centre correctly ;). I keep meaning to have a look at IronPython, not least because it’s obviously the way Python is going to go on Windows at some point in the future. Better be on the ball before the game starts. (If that’s the metaphor I want).