IMO this is not as much a framework comparison rather than an evaluation of the individual components that make up Pylons.
The framework is the sum of all its parts. Programmers should not need to know that that a package named Beaker is used for sessions, Routes for url mapping, PasteDeploy for whatever. This is the weakness of all glue-type frameworks i.e. TG and Pylons. It makes them look like they are duct-taped together. The more important question are whether the sessions actually work properly: i.e does session data persist through a server restart? Where is the session data stored: in memory, files, database and so on. The choice of templating language should be a non issue. Any half decent framework should allow you to use any other templating engine with ease. ... even python as you seem to prefer i. -- http://mail.python.org/mailman/listinfo/python-list
