pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gerhard Haering <haering_postgresql@gmx.de>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Cc: darcy@druid.net
Subject: Re: python bug
Date: Mon, 16 Dec 2002 03:51:21 +0100
Message-ID: <20021216025120.GB4825@gargamel.ghaering.test> (raw)
In-Reply-To: <200212150150.gBF1oEJ19799@candle.pha.pa.us>
References: <200212150150.gBF1oEJ19799@candle.pha.pa.us>

* Bruce Momjian <pgman@candle.pha.pa.us> [2002-12-14 20:50 -0500]:
> I saw this in the python source setup.py:
> 
>         include_dirs=['/usr/include/pgsql']
>         library_dirs=['usr/lib/pgsql']
>                        ^^^
>         optional_libs=['pq']
>         data_files = []
> 
> Is the lack of a leading slash correct?

No.

It should really be 

    library_dirs=['/usr/lib/pgsql']

*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 setup.py part of PyGreSQL, I'd recommend
you take a look at the setup.py file for our altnernative PostgreSQL/Python
adapter:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/pypgsql/pypgsql/setup.py?rev=HEAD&content-type=te...

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



view thread (3+ messages)  latest in thread

Message-ID: <20021216025120.GB4825@gargamel.ghaering.test>
Permalink:  ../20021216025120.GB4825@gargamel.ghaering.test/
Also on:    postgresql.org/message-id/20021216025120.GB4825@gargamel.ghaering.test

 · 

reply

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: haering_postgresql@gmx.de, pgman@candle.pha.pa.us, darcy@druid.net
  Subject: Re: python bug
  In-Reply-To: <20021216025120.GB4825@gargamel.ghaering.test>

* 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