On Mar 27, 2007, at 8:48 AM, Max Ischenko wrote:
> Hello, > > First thing I noticed when tried CherryPy 3 branch is that some > extensions don't work. In particular, TurboZSI which depends on > cherrypy's filters API. > > As a quick fix, I added code in r2803 to ignore such ImportErrors. > > The larger question is: while moving to CherryPy 3, is TurboGears > responsible for providing compatibility-layer API for clients or > let them break (like TurboZSI)? I don't think TG should do that because I believe it might be too complicated and will increase or codebase's size which is what our final goal is trying to avoid. Third-party extensions should adapt their obsolete dependencies with CP2 in the same way TG 1.1 is doing IMO. Anyway, I think that porting filters to tools is quite straightforward so it won't be much of a problem. Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
