-> >psycopg has worked well for me.  PoPy and PygreSQL both gave me trouble
->
-> Then there's the license angle to be taken care of, at least for those of
-> us who do not have the freedom to release under GPL the code we work on.
->
-> While PsycoPG and PoPy are released under the GPL, both PygreSQL (the
-> oldest one) and pyPgSQL (the newest one) have a liberal, BSD-like license,
-> similar to those of Python and PostgreSQL.
->
-> Apart from the known technical ones, the license is an important reason for
-> choosing which RDBMS to use in proprietary projects. It is unfeasible to
-> use MySQL (unless you are willing to pay for an alternative license); it
-> would be foolish to stick a GPL layer in the middle of BSD-like licensed
-> components, when there are alternatives.

FUD ;).  Dynamic linking with either psycopg or PoPy will not contaminate
your code, because they both implement an API and are not necessary
components of your application.  Only if you change their code directly
will you have to worry about their license.

--titus

Disclaimer: I'm a pretty big fan of the GPL, as is my institution (the
the holder of copyright on any work-related software I produce).  I don't
want to get into a discussion of its merits or lack thereof, but I would
like to make sure that people understand the position held by the FSF
lawyers with regards to the GPL's applicability and enforceability, because
there's a lot of confusion out there.