Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> I don't have a clear idea how to fix this in the long run. We would
> perhaps need to determine at which points the various platforms had
> fixed this issue in their Python installations and select between the
> old and the new approach based on that. Seems messy.
Are we sure it's an issue within Python, rather than something we
could dodge by invoking sysconfig differently? It's hard to believe
that sysconfig could be totally unfit for the purpose of finding out
the include path and would remain so for multiple years.
regards, tom lane
