| From: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net> |
|---|---|
| To: | sdavis2(at)mail(dot)nih(dot)gov |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: Python interfaces |
| Date: | 2006-09-15 18:51:40 |
| Message-ID: | 20060915145140.4cb86e12.darcy@druid.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Fri, 15 Sep 2006 13:52:20 -0400
Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> wrote:
> I am in the process of moving development from perl to python. Under perl,
> there was DBI, the be-all-end-all of database interfaces. Under python,
> there is a plethora of options. Is there a recommended one for postgres? It
> will be mainly used in a web environment, so the ability to work
> asynchronously is not that important. I am interested in maintaining
> database introspection (which the DB-API 2.0 is conspicuously short on)
> tools, as well as niceties such as automatic escape-quoting, etc, that are
> pretty standard in perl. Any suggestions?
I maintain PyGreSQL which used to be the one shipped with PostgreSQL
before we split it off into a separate project. http://PyGreSQL.org/.
--
D'Arcy J.M. Cain <darcy(at)druid(dot)net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeroen T. Vermeulen | 2006-09-16 08:57:38 | Re: Progress of asynchronous queries |
| Previous Message | Joshua D. Drake | 2006-09-15 18:30:37 | Re: Python interfaces |