From: D'Arcy J.M. Cain <darcy@PyGreSQL.org>
To: Gerhard Häring <lists@ghaering.de>
To: pgsql-interfaces@postgresql.org
Cc: award-postgresql@dominionsciences.com
Subject: Re: 7.4 and Pygresql
Date: Thu, 4 Dec 2003 06:41:03 -0500
Message-ID: <200312040641.03515.darcy@PyGreSQL.org> (raw)
In-Reply-To: <3FCEEC80.7000509@ghaering.de>
References: <32489.68.62.129.152.1070507821.squirrel@award.gotdns.org>
<3FCEEC80.7000509@ghaering.de>
On December 4, 2003 03:12 am, Gerhard Häring wrote:
> Arthur Ward wrote:
> > IMO,
> > this is quite an abominable situation for Python support;
>
> If you find PyGreSQL badly supported, you can use pyPgSQL or psycopg, which
> were founded for this reason, among others. PyGreSQL's state was the reason
> I hopped on board of the pyPgSQL development team two years ago.
>
> > it shouldn't have been pulled from the Postgres source tree if that
> > really was the only source for a current, usable version of the
> > interface.
>
> I suppose the GBorg project should be the definite place of the latest
> sources now.
>
> Also, PyGreSQL and PoPy (yet another Python adapter for PostgreSQL which
> seemed pretty badly supported to me) announced a merge of their projects a
> few months ago on DB-SIG (the Python database list). My personal opinion is
> that there's nothing worth keeping from the PyGreSQL codebase, and if you
> want a supported PostgreSQL adapter, you should really switch to pyPgSQL or
> psycopg.
You know, I expect that sort of FUD from commercial enterprises that have
something to gain by switching people to their product. I am especially
disapointed to see this from you, Gerhard, after the contributions that you
have made to PygreSQL in the past.
By the way, the main reason that we moved PyGreSQL out of the main source tree
was that we could not add PyGreSQL developers to the tree without getting
them full access to the PostgreSQL tree. This move, which was fully
supported by the rest of the PostgreSQL team, was made to allow PoPy
developers in particular to have direct CVS access to the PyGreSQL tree so
that we could try to de-splinter the PostgreSQL/Python community. Given your
support in the past you would also have been welcome as a member of that
team, something I was not previously able to offer. Even so, I have always
folded your patches in. You are even mentioned on the web site as a
contributor to the 3.2 release.
PyGreSQL is far from dead. There will soon be a new web site and we will be
putting out a new version soon. Meanwhile, the CVS repository is publicly
available and the current version works quite well with the current version
of PostgreSQL. Don't write us off just yet.
--
D'Arcy J.M. Cain
PyGreSQL Development Group
http://www.PyGreSQL.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: darcy@PyGreSQL.org, lists@ghaering.de, award-postgresql@dominionsciences.com
Subject: Re: 7.4 and Pygresql
In-Reply-To: <200312040641.03515.darcy@PyGreSQL.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox