Skip site navigation (1) Skip section navigation (2)

Re: Python API

From: Steven Erickson <stevererickson(at)gmail(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>,Volkan YAZICI <volkan(dot)yazici(at)gmail(dot)com>,pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Python API
Date: 2005-04-24 22:21:23
Message-ID: 11c11fe05042415212acba5b6@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
I'm currently using PyPgSQL and it is working fine. I don't use the libpq 
directly, but import pyPgSQL, which is a thin wrapper around the Python API.

On 4/24/05, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> 
> Michael Fuhr wrote:
> > On Sun, Apr 24, 2005 at 05:50:04PM +0300, Volkan YAZICI wrote:
> >
> >>I've used to program using psycopg for PostgreSQL connections. But
> >>I've just learnt that, ADOdb has Python support too. I tried to search
> >>the mailing list archives for alternatives but they seem very old
> >>(like discussions from 2003). I'd be so appreciated if somebody could
> >>share his/her own experiences for PostgreSQL Python APIs.
> >>
> >>List of PostgreSQL Python APIs which I know: PyGreSQL, psycopg, ADOdb.
> >
> >
> > There's also pyPgSQL but it doesn't appear to have been updated for
> > almost two years. Psycopg seems to get the most recommendations;
> > that's what I use.
> 
> I would use psycopg. It is what Command Prompt uses exclusively for its
> Python/PostgreSQL development. It is under reasonably active development
> and the author is responsive when we ask questions.
> 
> Sincerely,
> 
> Joshua D. Drake
> Command Prompt, Inc.
> 
> >
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/docs/faq
>

In response to

pgsql-interfaces by date

Next:From: Brett SchwarzDate: 2005-04-25 06:52:44
Subject: ANNOUNCE: pgtcl 1.5 beta 1 release
Previous:From: Joshua D. DrakeDate: 2005-04-24 18:02:46
Subject: Re: Python API

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group