I want to make TG2 be based on WebOb "from the beginning" so that we don't have to make a breaking change after we release it to a wider public.
I thought this was going to be a flip the switch kind of thing, but when Alberto took up the challenge it turned out to be more than we though. it turns out there are two WebOb incompatibilities in the current pylons trunk which need to be overcome. Here's what Alberto had to say: > This is turning out to be less of a trivial thing than I thought... :( I > couldn't manage to get tests to pass since Pylons needs some patching: > > 1) In DecoratedController req.params are immutable (hence no pop > or update can be done) > > 2) In pylons.testutil.SetupCacheGlobal WSGIRequest and WSGIRepsonse > frompaste are hardcoded and break when using webob. We can fix 1 easily, but I think it would be good to have a plan about how to handle 2, since we likely want testutil to work with both pylons request response objects and WebOb. It's also possible that there will be other issues after 2 is fixed which we haven't found yet since we're not yet to the point where the test infrastructure works to show us what else might be failing. -- 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 "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
