Bug? if PyGreSQL, inserttable is used followed by a for loop

[risadinha]

although the original post is more than a year old, I want to add:

I am experiencing the same behaviour as Anton:
After calling db.inserttable(...) the next for-loop breaks. If I comment
the db-methods, the script runs fine (except that it does not insert
anything...).

The PostgreSQL version is: 7.3.3
I have compiled PyGreSQL out of the source tree of 7.3.2.

So, isn't anyone else using inserttable in combination with loops, or
is PyGreSQL not maintained anymore (why is it then shipped with
Postgres?), or... ???

cheers,
Chantal

--
Posted via http://dbforums.com