| Developer(s) | Kevin Dangoor (original creator), Mark Ramm (TG2 lead), et al. |
|---|---|
| Stable release | 2.1.3 / September 28, 2011 |
| Preview release | none / n/a |
| Written in | Python |
| Operating system | Cross-platform |
| Type | Web application framework |
| License | MIT License, LGPL |
| Website | www.turbogears.org |
TurboGears is a Python web application framework consisting of several WSGI components such as Pylons, SQLAlchemy, Genshi and Repoze.
TurboGears is designed around the model-view-controller architecture, much like Struts or Ruby on Rails, designed to make rapid web application development in Python easier and more maintainable.
Contents |
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 alternate configurations. The following are the primary components a developer would interact with.
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,[2] 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.[3] However, the official TurboGears 2 documentation states that this is unlikely to happen, due to the "different, but compatible priorities"[4] 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).
TurboGears development is now focused primarily on the new 2.x branch, with version 2.1.3 recently released. The 1.x branch will continue to receive security and maintenance releases for the next few years. A future 1.1 release will change the default ORM and templating language to match the 2.x series as a means of transition. The planned 1.5 release that would update CherryPy to version 3 has now been canceled to make 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 [1] project.
The lead developers of TurboGears are now in talks with the Pylons project to join forces with them and Repoze.BFG's developers as a new unified project called Pyramid. The idea is that Pyramid will act as the core base, with minimal dependencies and then TG 3 or TurboPyramid or Orion (name still being discussed) will be a full-stack option built on top of Pyramid. If the merger does occur, it will mean a much larger development community for Turbogears and the current team has promised to make the transition from TG2 as easy as possible.
Until TG3 / TurboPyramid / Orion come to pass, though, the TurboGears community continues work on the TurboGears 2 project.
Ramm, M; Dangoor, K; Sayfan, G (November 7, 2006). Rapid Web Applications with TurboGears, Prentice Hall. ISBN 0132433885
|
|
|||||
|
||||||||||||||||||||||||||||||||||||||