[kforge-dev] Re: testing kforge

[Rufus Pollock]

John Bywater wrote:
> Hey Rufus,
> 
> The suite kforge/urltest.py produces this error  (see below for the test 
> report):

Thanks for the info.

> AttributeError: 'unicode' object has no attribute 'decode'
> 
> 
> Any ideas about what's gone wrong?

I can't reproduce this locally (i.e. all tests pass). I note i'm using 
Routes 1.6 rather than 1.7. I'll try investigating further.

> Also, would you like to arrange a time to meet this week?

Yes. I'll give you a call.

> Best wishes,
> 
> John.
> 
> PS The only other test failures (`kforge-test 
> kforge.handlers.projecthosttest`) arise from the fact that the handler 
> return code(s) were changed. I guess the tests have been failing since 
> the access handler return code(s) was changed from 0 to 403. But are we 
> happy with this aspect, what doesn't it do?

I think we need to look into this a bit more. This arose from changes to 
eliminate the bug whereby people could still post even though not 
authorised too (See comments in the handlers/projecthost.py). My 
recollection is that the changes led to some weird behaviour (like a 500 
error rather than a simple 401).

~rufus