|Developer(s)||Kevin Dangoor (original creator), Mark Ramm (TG2 lead), et al.|
|Initial release||September 2005|
|Stable release||2.3.4 / 3 October 2014|
|Type||Web application framework|
|License||MIT License, LGPL|
TurboGears is designed around the model–view–controller (MVC) architecture, much like Struts or Ruby on Rails, designed to make rapid web application development in Python easier and more maintainable.
TurboGears is built on top of numerous disparate libraries and middleware. The default tools have changed between the 1.x and 2.x series, but most of these components can be used in either as there is support for many alternative configurations. The following are the primary components a developer would interact with.
TurboGears 2.x components
- SQLAlchemy (Model) - defines the table structures of the user's database and how to link them to Python objects the user's controller can interact with.
- Genshi (View) - defines templates for the HTML or XHTML the user will generate. This is where the user defines the front-end the client will interact with.
- Pylons (Controller) - this middleware handles all the user's back-end logic and connects to the user's webserver to offer up data to the web. By default, the Paster webserver is used, but the user can also connect to Apache, Nginx, or any other WSGI-compatible webserver.
- Repoze - Repoze.who & Repoze.what are used to handle security (authentication & authorization respectively). When defining elements of the user's controller to be exposed to the web, repoze predicates define who can access them and under what conditions.
TurboGears 1.x components
- SQLObject (Model) - data backend that can create a database or interface with existing data on many database servers.
- SQLAlchemy is slated to become the default in TurboGears >= 1.1.
- Kid (View) - XHTML frontend templating engine where all templates are valid XHTML or XML files that are usually made in a way that allows opening these templates as simple XHTML files to check the design. At the same time features are provided to embed snippets of Python in a XMLish manner.
- Genshi is the successor to Kid and will replace it as the default templating engine in TurboGears >= 1.1. It is nearly 100% syntax-compatible to Kid.
- CherryPy (Controller) - middleware that allows web applications to be programmed by writing event handlers that return data to (in TurboGears case) templates. The same data can also be received in Ajax fashion as a JSON data stream.
Templating languages other than Genshi can be used through the user's app's configuration file. Plugins currently supported in 2.1 are Myghty, Jinja2, Mako, Cheetah, and Kajiki. Kid support is not currently planned as Genshi is virtually identical. This list may continue to change in future versions.
TurboGears was originally created in 2005 by Kevin Dangoor as the framework behind the as yet unreleased Zesty News product. When he released it as an open source framework in the end of September 2005, it received more than 30,000 screencast downloads in the first 3 months.
January 2007 Kevin Dangoor retired as project leader and Alberto Valverde managed the project as his successor, but subsequently stepped down due to other personal commitments. Alberto is still involved in the TurboGears community through his ToscaWidgets project. The TurboGears project is now managed jointly by a group of about half a dozen core developers under the leadership of Mark Ramm (as the TurboGears 2 development lead) and Florent Aide (as the Turbogears 1.x release manager).
In June 2007 the community began experiments to put the TurboGears API on top of components and protocols used in Pylons and there was speculation that the two frameworks may finally be merging. However, the official TurboGears 2 documentation states that this is unlikely to happen, due to the "different, but compatible priorities" of both projects. Pylons wanted to stay focused on low level, extensible design while Turbogears was focused on offering a complete, user-friendly package, and so the two work together much in the same way Debian and Ubuntu do now. The new 2.x branch had its first stable release in May 2009.
As of Fall 2008, TurboGears has a large and healthy community with over 3000 users on the TurboGears mailing list, a book from Prentice Hall published in Nov. '06, and a number of open source and proprietary TurboGears applications deployed to the real world. The development progresses at a moderate but steady pace and was also newly fueled by a successful participation of the project as a Google Summer of Code mentoring organization in 2008 and 2009. TurboGears 1.1, aimed at helping legacy sites make the transition to 2.x, was released in October 2009. A new revision of the book is in the works to update it in line with the changes TurboGears 2 has brought.
In 2010, the project faltered somewhat. The lead developers were called away due to real life issues. By the end of Jan, 2011, though, the project had begun reorganizing and working on getting back on track. After several months getting infrastructure in order and working through coding issues, TurboGears has managed to release new versions (2.0.4 and 2.1.2).
In 2013, while maintaining backward compatibility, the project has moved away from the Pylons codebase to support Python3, provide speed ups and an easier install process. This lead to the release of version 2.3.0 in August 2013. It has also been announced a faster release cycle which should lead to a maintenance release every ~3 months.
Future of TurboGears
TurboGears development is now focused primarily on the new 2.x branch, with version 2.2.2 recently released and 2.3 preview release with Python3 support. The 1.x branch will continue to receive security and maintenance releases for the next few years. A transition path from the 1.x branch to the 2.x branch is provided through the 1.1 and 1.5 releases which moved the default ORM and templating languages to match the one used by the 2.x series. The TurboGears team made it clear to new users that 2.x is the future, and 1.x is merely maintained for the convenience of existing users. For users interested in continuing down the path of 1.x and wanting to use CherryPy3 a friendly fork has emerged in the GearShift  project.
The lead developers of TurboGears have been in talks with the Pylons project to join forces with them and Repoze.BFG's developers as a new unified project called Pyramid. Due to the backward compatibility issues this move would have, and to make TurboGears a reliable platform for the future, the current team decided to collaborate with the Pylons Project on everything possible but not to base the TurboGears core on Pyramid.
Future development, Python3 support and speed improvements have happened in the 2.3 branch which has seen a full rewrite of the TurboGears core while keeping it backward compatible with existing applications, since that release TurboGears will feature its own core instead of being based on the legacy Pylons framework.
- Ramm, M; Dangoor, K; Sayfan, G (November 7, 2006). Rapid Web Applications with TurboGears, Prentice Hall. ISBN 0-13-243388-5
- ToscaWidgets Cookbook — TG2 v2.0 documentation
- "TurboGears has a new leader". Kevin Dangoor. 2007-01-03. Retrieved 2007-04-12.
- "Pylons Merge". Retrieved 2007-06-27.
- "What’s new in TurboGears 2". Retrieved 2008-09-16.
- python-gearshift - The GearShift Python Web Framework - Google Project Hosting. Code.google.com. Retrieved on 2014-05-30.
- "State of the Gears". Michael Pedersen. 2012-03-01. Retrieved 2013-03-18.
- "TurboGears 2.3 unstable release". Alessandro Molina. 2013-01-23. Retrieved 2013-03-18.
- TurboGears homepage
- TurboGears Blogs
- TurboGears google group
- TurboGears screencasts and related videos at showmedo
- TurboGears from start to finish