The WebOb tests seem to all pass. But there seems to be some kind of recursion loop problem that shows up in both the pylons and TG2 tests.
You can see the traceback here: http://paste.turbogears.org/paste/1932 I won't have much time to look into until tonight. But I'll try to dig in a bit more then and see what information I can find. --Mark On Jan 31, 2008 1:37 PM, Ian Bicking <[EMAIL PROTECTED]> wrote: > Sorry I haven't gotten back to you about this stuff earlier; my computer > went down and I'm just now getting back up. > > Mark Ramm wrote: > > I made a very small change to HTTPException that helped me get nearly > > all the pylons tests running on trunk. Obviously this isn't the > > right way to solve the larger problem, but I think it does point us in > > the right direction. Basically I added these two lines to > > HTTPException's __init__ method: > > > > self.headers = self.wsgi_response.headers > > self.set_cookie=self.wsgi_response.set_cookie > > > > That way when Pylons tries to set the headers or throw some cookie > > information on the HTTPException instance, it just works. > > > > Seems like a little bit of __getattr__ trickery and we can expose > > pretty much all of the expected API. > > Yeah, I was thinking about that too. That could certainly go in WebOb. > > I gave a first run at it in the trunk just now (r7196). But I don't > have a Python 2.4 test rig currently, so I only know it doesn't break > Python 2.5 (though actually everything is basically commented out for > Python 2.5, so "not breaking" doesn't say much). > > Can you test this out? > > Ian > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog _______________________________________________ Paste-users mailing list [email protected] http://webwareforpython.org/cgi-bin/mailman/listinfo/paste-users
