[kforge-dev] Re: testing kforge

[John Bywater]

Rufus Pollock wrote:

>> AttributeError: 'unicode' object has no attribute 'decode'
>
>
> 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.


Would it be fixed if we made the dependency a little narrower?

>> Also, would you like to arrange a time to meet this week?
>
>
> Yes. I'll give you a call.


Fab.


>> 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).


Sure, let's look into it a bit more.

See you later,

John.


>
> ~rufus
>