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

Re: python bug

From: Gerhard Haering <haering_postgresql(at)gmx(dot)de>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-interfaces <pgsql-interfaces(at)postgresql(dot)org>,darcy(at)druid(dot)net
Subject: Re: python bug
Date: 2002-12-16 02:51:21
Message-ID: 20021216025120.GB4825@gargamel.ghaering.test (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
* Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> [2002-12-14 20:50 -0500]:
> I saw this in the python source
>         include_dirs=['/usr/include/pgsql']
>         library_dirs=['usr/lib/pgsql']
>                        ^^^
>         optional_libs=['pq']
>         data_files = []
> Is the lack of a leading slash correct?


It should really be 


*But* is this really the default place where PostgreSQL installs its
libraries?  I thought this was rather /usr/local/lib?

If anybody wants to improve the part of PyGreSQL, I'd recommend
you take a look at the file for our altnernative PostgreSQL/Python

We recently put considerable effort in to make pyPgSQL build out of the box
on many platforms (Debian, SuSE, Redhat Linux, FreeBSD, OpenUnix, Windows,
MacOS X, Cygwin plus untested support for a few other platforms).

And of course pyPgSQL is licensed under a liberal BSD-like license as well

Btw. another question. I noticed that a few interfaces (Perl comes to mind)
have been moved out of the PostgreSQL tree to gborg. Maybe it'd be a good
idea to do that for PyGreSQL as well?

-- Gerhard

In response to

  • python bug at 2002-12-15 01:50:13 from Bruce Momjian


pgsql-interfaces by date

Next:From: Tom LaneDate: 2002-12-16 18:13:26
Subject: Re: AsciiRow
Previous:From: Bruce BadgerDate: 2002-12-16 00:24:21
Subject: AsciiRow

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