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

Re: python cleanup

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: python cleanup
Date: 2011-07-25 14:18:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

On 07/24/2011 11:46 PM, Tom Lane wrote:

[python headers set _POSIX_C_SOURCE and _XOPEN_SOURCE]
> What in the world are the python headers doing fooling with these
> macros, anyway??
Good question.	It seems unfriendly. It looks like you're just about guaranteed to get a warning if you include any system header before you include Python.h.

So either we have to dance around that or we have to give up the idea that postgres.h must come first. It wouldn't be the first time we've had to do that sort of dance.

The reason we get warnings about these and not about many other things it defines (such as the HAVE_foo macros) is that these are set to values different from those encountered in the previously included headers.



In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2011-07-25 14:30:52
Subject: Re: python cleanup
Previous:From: Robert HaasDate: 2011-07-25 13:39:02
Subject: Re: Questions and experiences writing a Foreign Data Wrapper

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