> As I understand it, TG will drop CherryPy, and adopt Pylons. Since > both frameworks are stacks of other python components, I am not sure > if I see the point. > > A strength of both tg, and pylons, is that you can easialy swap out > different compents, right? So why not just put together whatever > components you want?
TurboGears will be what it has always been, a stack of best of breed python components, wired together to provide a web experience that gets you started quickly, and provides a robust web development environment. TurboGears 2 will provide Pylons with a set of standard components, a new controller publishing API that is easier to get started with than Routes, a bunch of additional rapid web development tools, and a lot more developer attention. Pylons provides a robust WSGI stack, and a clean way to reimplement the TurboGears API in relatively little code. And since Pylons has a goal of being a framework that maximizes developer choices, people have been pushing Ben and the rest of the pylons dev's to make a well documented set of defaults, and to make the framework a bit easier for new developers to learn. In the new TurboGears+Pylons working together world, we're both able to focus on the things that have made our individual frameworks successfull in the past, and share development effort on lots and lots of things. So do answer your point, I think that working together with the Pylons folks benefits everybody in both user communities, and helps to strengthen both frameworks. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
