Posts

Routes has been a wonderfully successful project of mine as its used not just in Pylons but quite a few other small WSGI apps. It's even been integrated as a CherryPy URL dispatching option for those using TurboGears 1.

I've been seeing more and more movies I wouldn't mind actually buying… except that I have a 56" HD TV set. It looks amazing, pretty good with DVD's, but really amazing with HD so if I'm going to buy a movie I sure as heck want it in HD.

Finding out whats going on in an application is always a key point when trying to figure out what's happening when things don't go the way you expect. In these kind of annoying situations, following the log of how your request mapped in and what was going on can save a significant amount of time.

Sometimes, it amazes me whats possible fully utilizing WSGI middleware in an application stack. While it likely isn't something totally unique to the framework, the relative ease with which it can be done still sometimes gets me to grin.

In light of Phillip Eby's recent post concerning WSGI Middleware as harmful, I've had more than a few thoughts on the issue. None of them are all that new, but given the post I think its useful to get some of them out there.

I remember reading a sci-fi book (David Brin's Earth) awhile back set in the near future where a man-made black-hole fell into the center of the Earth. To say the least, it created a bit of a problem for our fictional heroes.

It's with great pleasure that I announce the release of Pylons 0.9.4. This release has quite a few bug fixes and enhancements, the most since the 0.9 milestone. It's also likely one of the last big updates before a 1.

For those that haven't gotten on the WSGI bandwagon, are still confused about Paste, how it fits into Pylons, and how its used in frameworks; I gave a Google Techtalk last week that hopefully can clear a few things up.

This is slightly old as Routes 1.4 was released about a week and a half ago, but I thought it deserved some attention. There were a handful of fixes and some slightly major feature enhancements in 1.

Last week during OSCON 2006, I was able to get a release of Pylons out. This version had some big internal changes, no longer using custom Myghty resolvers. We now use a very straight-forward WSGI interface to setup the application and the middleware.