Re: apply pragma system_header to python headers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: apply pragma system_header to python headers
Date: 2023-11-06 14:57:00
Message-ID: 3831479.1699282620@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> Analogous to 388e80132c (which was for Perl) but for Python, I propose
> adding #pragma GCC system_header to plpython.h. Without it, you get
> tons of warnings about -Wdeclaration-after-statement, starting with
> Python 3.12. (In the past, I have regularly sent feedback to Python to
> fix their header files, but this is getting old, and we have an easier
> solution now.)

+1 for the concept --- I was just noticing yesterday that my buildfarm
warning scraping script is turning up some of these. However, we ought
to try to minimize the amount of our own code that is subject to the
pragma. So I think a prerequisite ought to be to get this out of
plpython.h:

/*
* Used throughout, so it's easier to just include it everywhere.
*/
#include "plpy_util.h"

Alternatively, is there a way to reverse the effect of the
pragma after we've included what we need?

(I'm not too happy about the state of plperl.h on this point, either.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Kukushkin 2023-11-06 14:58:56 Re: pg_rewind WAL segments deletion pitfall
Previous Message Stephen Frost 2023-11-06 14:56:37 Re: Moving forward with TDE [PATCH v3]