The autocommit bug with psycopg2

Hi,

sorry if this is an old topic, but I did not find any list
archive.  I just took up using SQLObject a few weeks ago;
very convenient.

I wonder if anyone has experience with a bug where the
the postgress connection attempts to call a boolean
value (autocommit) as a method.  (Call stack is cut in below.)
It is not a new problem, I found it reported here as well:
http://stackoverflow.com/questions/6374121/python-why-does-sqlobject-fail-in-conn-autocommit1

What is odd is that my code works fine on Ubuntu 10.4 with a connection
to localhost.  When I run the same code on Ubuntu 10.10 with a remote
server, it fails.  I am not sure if the difference is with the
remoteness or the software version ... So far I have tried to make do
 with the standard ubuntu packages for sqlobject and postgres.

Does anyone know if this problem has been resolved in some recent 
version of sqlobject/psycopg?  Or if there is a known workaround?
I do observe that the URL below suggests what looks like a 
downgrading of psycopg2, which I won't do if upgrading is an option 

My call stack is:
  File "/home/georg/git/pysteg/src/pysteg/sql/tables.py", line 346, in
getJob
    trans = conn.transaction()
  File "/usr/lib/pymodules/python2.7/sqlobject/dbconnection.py", line
400, in transaction
    return Transaction(self)