I've been steeped in Pylons for several years now. I agree that Pylons has nothing to get excited about. However, (and this is the important part) it provided really straightforward glue to integrate a few other things that are definitely worth getting excited about: SQLAlchemy, Mako/Jinja, Routes, Beaker, and Paste.
Pylons' past philosophy always seemed to be "we'll take the best-in-breed of python web software and put it together in an elegant way." Sadly, they seem to have abandoned that philosophy for the sake of protecting the precious nest eggs of massive full-stack framework developers.
While the new changes to Pylons certainly don't prevent you from using the aforementioned exceptional-quality components, the smushing-together of projects while trying to retain legacy compatibility seems to have created an enormous system where there isn't a cohesive or consistent way of doing things.
No thanks--I think I'll go for WebOb and its lightweight performance.
Pylons' past philosophy always seemed to be "we'll take the best-in-breed of python web software and put it together in an elegant way." Sadly, they seem to have abandoned that philosophy for the sake of protecting the precious nest eggs of massive full-stack framework developers.
While the new changes to Pylons certainly don't prevent you from using the aforementioned exceptional-quality components, the smushing-together of projects while trying to retain legacy compatibility seems to have created an enormous system where there isn't a cohesive or consistent way of doing things.
No thanks--I think I'll go for WebOb and its lightweight performance.