Hi Jordan, that should work in twill! It does with 40x; maybe the 50x error isn't handled properly... hmm, well, '500' is tested (see "tests/test-http-codes.twill"), so that presumably works ;).
I have to dig into quixote, my test server framework, to figure out how to generate a 503 error. So I can't test it right away. But HTTPErrors should be caught by twill properly, so this is definitely a bug in twill. Ping me if it's urgent and I'll do it today, otherwise sometime this week I hope. cheers, --titus On Tue, May 01, 2007 at 10:55:59AM -0400, Jordan Baker wrote: -> Hi folks, -> -> Trying to use twill to test a page that returns an HTML page with a 503 -> response code. -> -> Here's my twill code: -> -> go http://server/page_returns_error -> code 503 -> notfind "some string" -> -> It seems that urrllib2 is returning an HTTPError even though a fully -> formed HTML page was generated and is visible via a regular browser. -> -> I started to poke around a bit and it seems that it might be possible to -> get around this by providing your own opener to urllib2 but I thought -> I'd check this list first to see if anyone had suggestions. -> -> Cheers, -> -> -jordan. -> -> -> _______________________________________________ -> twill mailing list -> [email protected] -> http://lists.idyll.org/listinfo/twill -> _______________________________________________ twill mailing list [email protected] http://lists.idyll.org/listinfo/twill
