Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e9AL6pJ29792; Tue, 10 Oct 2000 17:06:51 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e9AL6eB20510; Tue, 10 Oct 2000 17:06:40 -0400 (EDT) To: "Billy G. Allie" cc: Peter Eisentraut , pgsql-interfaces@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [INTERFACES] Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQL In-reply-to: <200010102045.e9AKjhk28688@bajor.mug.org> References: <200010102045.e9AKjhk28688@bajor.mug.org> Comments: In-reply-to "Billy G. Allie" message dated "Tue, 10 Oct 2000 16:45:43 -0400" Date: Tue, 10 Oct 2000 17:06:40 -0400 Message-ID: <20507.971212000@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/291 X-Sequence-Number: 7317 "Billy G. Allie" writes: > Peter Eisentraut wrote: >> Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of >> name, given that it's already used as an abbreviation for "PostgreSQL"? > PgSQL is the name of the module you import in Python to access a PostgreSQL > database from Python using the DB-API 2.0. The project name on SourceForge > is "Python Interface to PostgreSQL". Of course, it there is too much heart > burn with the modules name, I can change it. FWIW, my initial reaction was the same as Peter's: that name is certain to cause confusion. I don't want to try to force you to change it, but I think it's not a good choice. Don't have a better alternative to offer offhand, however. regards, tom lane