TurboGears 2 is built on top of the experience of several next generation web frameworks including TurboGears 1 (of course), Django, and Rails. All of these frameworks had limitations that frustrated us, and TG2 was built as an answer to that frustration.
Ranked in these QuestionsQuestion Ranking
Pro A powerful and flexible Object Relational Mapper (ORM) with real multi-database support
SQLAlchemy is a powerful ORM which is highly regarded in the Python community. TurboGears' ORM is built with SQLAlchemy, which gives it a great deal of flexibility and power.
Pro Code that is as natural as writing a function
Pro Starts as a microframework and scales up to a fullstack solution
Allows developers to build quick, simple web prototypes or scale up to create complex web applications.
Pro Support for Horizontal data partitioning (aka, sharding)
TurboGears allows for horizontal data partitioning, which allows the division of logical datatabases into smaller elements.
Pro Built in extensibility Pluggable Applications and standard WSGI components
Allows for creating extendable Pluggable Applications which extend the framework itself through endpoints provided by TurboGears.
Pro Validated and compile time checked template engine
The template engine is XHTML based and so is validated for errors when compiled to HTML. You will never serve a broken page again due to a forgotten close tag
Pro Aims for a flexible design
TurboGears2 does not get in your way on how to design your applications, classes etc.
Con The great extensibility can feel overwhelming
Sometimes TurboGears' extensibility and feeling of having different options for doing a single thing can feel overwhelming and as if writing everything from scratch.