Milestone 2.0

TurboGears 2.0 involves a serious (but mostly backwards compatible) shakeup of the project foundations in order to support pervasive Python WSGI capabilities. What this ultimately means is a great deal more flexibility in combining and reusing TurboGears applications plus applications and "middleware" developed at other projects!

TurboGears 2.0 will be based on Pylons 1.0 , and will replicate the core turbogears api as closely as is feasable. In some cases, we will make backwards incompatible changes in order to clean up API's, or because they are not reasonable given our new foundation.

The TurboGears decorators will be maintain the same API, but will be rewritten to regester information in the application, and the functionality to implement their behaviors will be housed in the TurboGears base controller. One small exception to the API stability rule, is that we will be implementing an improved content negotiation system for the stacked exposed decorators.

The new system will allow content type choices via accept headers, dotted extensions to the url (index.html indicates that a user wants html, while indeex.json indicated that the user wants the call to return JSON, and index.rss indicates a desire for an RSS feed, dotted extensions will override accept headers, and the tg_format parameter will allow you to overide both by passing explicitly requesting a particular parameter.

There will also be enhancements to the Identity system, and perhaps other TG comonents, as well as a brand new toolbox, which is will contain various new TurboGears tools.