On Mar 27, 2007, at 2:48 AM, Max Ischenko wrote: > 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.
Though I haven't tested it, there's a good chance that TGWebServices will work with CP3 directly, as it doesn't involve filters. Obviously, if you have a bunch of code that depends on TurboZSI, this doesn't help you. > 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)? > That probably needs to be decided on a case-by-case basis. Obviously, as much as possible it's good to maintain backwards compatibility... but we can't let all forward progress stop in the name of backwards compatibility either. CP filters is one area where we knew there would be breakage. It may be possible to make a CP3 tool that emulates the filter interface. That is the kind of thing that is best driven by someone who needs that backwards compatibility. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
