Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9re9-0002d3-7j for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jan 2022 16:47:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n9re7-0000It-Q2 for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jan 2022 16:47:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9re7-0000Ik-G8 for pgsql-hackers@lists.postgresql.org; Tue, 18 Jan 2022 16:47:47 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9re2-0008Eu-P3 for pgsql-hackers@postgresql.org; Tue, 18 Jan 2022 16:47:47 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2F4EF5C0524; Tue, 18 Jan 2022 11:47:41 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 18 Jan 2022 11:47:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=bM11FRhqQXRmkH49E6sBAmxGYNebWxKV/3vOO5TXb 2E=; b=kKiTje62m/ya6kFMdJup3etqxSU2w+5Dob1MBR+HcpvEizx5VSBYPpIRu A0jsb1ubU1ey0SkJspnpvIExL7zMv1zCXOgjmP30+bKDnKeVexdtrElIwZmqlIfS 7Rur3bGQL4frH9JBSraIa3/2qfDb7HphK/v6yQM/yhRJVQobK+fN/HJVySFcH4cK nQTK2Ya3/WqWbGKBxe6RsvTzBIBp2PZBVuzX5SFi2qwKuM1mDliIP1ygmBrSom9x aHe9QwFuKtgiTuOqOsEjoHHJVKmV/JKa1HywDYv1FRJB+B5h7/L/V0TflteIcWL9 CJNlaFWmuMghOvG0tdw7JbN6hEjWQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefgdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejre dttdefjeenucfhrhhomheprfgvthgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdr vghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusgdrtghomheqnecuggftrfgrth htvghrnhepvdeiteegffdvudejfffhgeffhfejvdduleduieehuedvleettdejffehieef teeunecuffhomhgrihhnpehphihthhhonhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 18 Jan 2022 11:47:39 -0500 (EST) Message-ID: <7129af76-acf6-f4d5-0de6-a479f75d8ad7@enterprisedb.com> Date: Tue, 18 Jan 2022 17:47:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Replace uses of deprecated Python module distutils.sysconfig Content-Language: en-US To: Tom Lane Cc: pgsql-hackers References: <0cd3579e-7790-aa05-0202-c6ce14d0af73@enterprisedb.com> <3777643.1639056683@sss.pgh.pa.us> <312939.1642519464@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <312939.1642519464@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 18.01.22 16:24, Tom Lane wrote: > Peter Eisentraut writes: >> Also, considering the failure on prairiedog, I do see now on >> 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.