On 18.01.22 16:24, Tom Lane wrote:
Peter Eisentraut <peter.eisentr...@enterprisedb.com> writes:
Also, considering the failure on prairiedog, I do see now on
<https://docs.python.org/3/library/sysconfig.html> that the sysconfig
module is "New in version 3.2". I had interpreted the fact that it
exists in version 2.7 that that includes all higher versions, but
obviously there were multiple branches involved, so that was a mistaken
assumption.
Hm. I installed 3.1 because we claim support for that. I don't mind
updating to 3.2 (as long as we adjust the docs to match), but it seems
kinda moot unless you figure out a solution for the include-path
issue. I see that platforms as recent as Debian 10 are failing,
so I don't think we can dismiss that as not needing fixing.
I have reverted this for now.
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.
