Re: State of PostgreSQL's drivers in Python

On Mon, Feb 8, 2010 at 05:55, Federico Di Gregorio <fog-NGVKUo/i/[email protected]> wrote:

> On 08/02/2010 00:46, Cezary Statkiewicz wrote:
> >  And a summary:
> >
> > http://it.toolbox.com/blogs/database-soup/postgres-needs-a-new-python-
> > driver-36815
>
> Most of what he says is wrong.


It would be interesting if someone would take it point by point as to what
they believe to be incorrect (he doesn't really make that many
non-subjective claims, so it's interesting that you state that it's mostly
wrong).  From the perspective of someone who has dealt with most of these
drivers (although not the Python 3 driver, which may be great, but many of
us aren't in a position to use Python 3) over the last few years, the points
seem pretty much on target (if broad).  In my experience pyscopg2 is
definitely the best, but the documentation is this mailing list and the
source code - which is to say, non-existant.  The license is also less than
desirable for many open source projects, let alone the ambiguity of the
commercial option.

Of course, the license "problems" are a matter of perspective - this license
may be very much what you intend and that is perfectly fine, but you have to
realize that it is a constraint for adoption, especially given a situation
where both Python and PostgreSQL have significantly more flexible license
terms.

--
Nick

_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/[email protected]
http://lists.initd.org/mailman/listinfo/psycopg