Well, I'd definitlely support people who want to work on CP3 integration in the TG 1 line. But you're right I don't have a need for it personally, and probably won't be working on it given the need for development effort on TG2, which I believe will bring greater rewards to the platform.
The main issues with TG 3 integration are updating the TG configuration system which was very closely coupled to CP 2.x behavior, and updating the test helpers in TG which depended on a CP 2 interface which is gone in CP3, and which were implemented by monkeypatching parts of CherrryPy. If you or others want to work on those issues, we still have the work we'd done so far in a branch in SVN, and I'm sure we'd support your efforts to get that branch working with CP3. And I'm sure the core folks will help as much as we can given our other TG commitments. --Mark > Would someone mind enumerating the difficulties with upgrading TG1.x > to support CherryPy 3 ? > > If there's any community say in the matter, I'd like to throw a +1 > into trying to support CP 3, if it is possible (and enough people > were willing to help work on it, without significantly effecting TG2 > development, which I assume will be the major focus of the core > developers). In my business we develop and support web applications > built on a combination of CP2, CP3 and TG, and would like to simplify > our support efforts by moving all apps to CP 3 only, if we can. > > Cheers, > Chris Miles > > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
