On 2/10/06, Mike Orr <[EMAIL PROTECTED]> wrote: > > Not sure if this can be done quite as soon as the sprint, but I'd like > to see some more convergence between TurboGears and Paste. TG > piggybacks on CherryPy's configuration system, and Paste has a > different system. People recently brought up RhubarbTart, and > CherryPy's filters vs Paste's middleware. It looks like > interoperability between projects is the best for the long term, the > same way that template plugins were seen as a minor good but turned > out to have significant unexpected benefits in addition (TurboStan, > etc). I don't know whether CherryPy's configuration system is better > or worse than Paste's, or filters are better/worse than middleware, > but it's a shame to have two incompatible pairs of systems, and > perpetuating them just makes it harder to interoperate in the long > run.
This is the kind of big-ticket item that I'd like to talk about at the Sprint... to at least knock around some ideas, if nothing else. It's also worth noting the presence of CherryPaste and additional new work that has gone on with CP's WSGI support. There are now a number of potential ways to get access to WSGI middleware and other applications, and those are worth considering. At this point, TurboGears has diverged a bit from CherryPy's configuration system. TurboGears' config is now contained in mildly special Python modules. I'd like to stick with this config system going forward, because it provides some capabilities that people have wanted beyond purely static config files. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
