[SQLObject] Python3 port status update

For those not following github closely, there has been good progess on
the port to python 3. We are now down to only 3 test failures with
python3 and sqlite, and 4 with postgres. No-one's looked at trying to
run against mysql yet, I believe.

The failures in test_unicode are due to the changed unicode handling
in pyton 3, and the tests should probably be reworked for the python 3
behaviour.

The fialure in test_validiation is due to the handling of a custom
class with a __unicode__ method. I'm personally not sure how we should
handle these in python 3. Would it help people porting code to special
case __unicode__ in this case, or should we expect people to update to
using __str__ ?

Regardless of the outstanding test failures, I think the port is at a
point whee it would benefit from more people using and looking at the
code.

-- 
Neil Muller
drn...@gm...

I've got a gmail account. Why haven't I become cool?