Code

It's been a busy month for Pylons, with lots of changes for the big internal API change in 0.9. The great news for those making Pylons apps right now with 0.

Finally pushed out release 0.8 of Pylons, a bunch of great features bundled up in a slick package that makes web development easy and brings re-use to new levels. I'm not going to repeat the full announcement here, but I'd suggest checking it out if you're the slightest bit interested in a framework leveraging WSGI for re-use and ease of use.

I got Routes 1.2 out the door today, it's a fairly important update for 2 reasons: A bug crept in with 1.1 using the default controller directory scanner. The scanner wasn't properly retaining the directory prefix which causes mismatches when using controllers underneath a sub-directory.

Ruby's anonymous block capability is probably the main feature I find myself wishing Python had on more than one occasion. While the upcoming Python 2.5 PEP 323 provides for the “with” statement which will enhance generators to get a bit closer.

I've released Routes 1.1 today after extending the unit tests for the new Groupings syntax and updating the docs. The new syntax is quite powerful and will hopefully make everyone using Routes rather happy.

The major feature I was waiting on for Routes 1.1 is for the most part done, mainly adding more unit tests for the new syntax now. As I mentioned previously when announcing Routes 1.

In a prior post on handling form data I covered how to easily populate a form using FormEncode/SQLObject and validate/save the data. One of the things I noted was that I had to take the HTML form output first, and use htmlfill with it to populate it with defaults and errors before displaying.

I've finally finished the documentation for Routes and as I mentioned earlier regarded releases am now ready for a 1.0 release. If you're curious about Routes and want to get up to speed, I'd suggest jumping straight to the Routes Manual.

One of the advantages to using SQLObject is that the code you write in it can easily be constructed in a way that ensures it'll work without a problem in all the databases SQLObject supports.

I've come to the belief lately that the web frameworks available in Python are increasingly fine-tuned to specific application requirements. Of course, anyone reading the ‘About' sections for these frameworks should realize this as well.