> > the TurboGears 1 Team will concentrate on preparing a beta > > release of the 1.1 branch and only critical bug-fixes will still be > It's a good time to discuss about change the cherrypy version from 2 to > 3. > I know that the first try was done some time ago and developers have > decided to stop migration, but, looking for cherrypy 3 features, maybe > the benefits pay the work.
If people are willing to help, we're willing to try to make this happen in 1.1. I think the key things are 1) test infrastructure updates and 2) updating the Turbogears configuraiton system to break it out of cherrypy. I think there are plans already to work on issue 2, and if somebody is willing to integrate paste.fixture style testing into TG 1.1, that will be a benifit as people move their apps from 1.1 to 2.0. Once those two things are done, I *THINK* cherrypy 3 integration will be reasonably simple. And I agree, cherrypy 3 is wicked awesome. ;) So, please people pitch in and help. Heck you can even help by writing SQLAlchemy and Genshi docs for 1.1 on docs.turbogears.org, so the main dev team has more time to work on core stuff. --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 -~----------~----~----~----~------~----~------~--~---
