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 1n7YE8-0006Ks-38 for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jan 2022 07:39:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n7YE6-0000SO-JM for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jan 2022 07:39:22 +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 1n7YE5-0000S9-9K for pgsql-hackers@lists.postgresql.org; Wed, 12 Jan 2022 07:39:22 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7YDv-00058S-Mn for pgsql-hackers@postgresql.org; Wed, 12 Jan 2022 07:39:20 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 566423200E1A; Wed, 12 Jan 2022 02:39:07 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 12 Jan 2022 02:39:07 -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=WzDwX8RrUB5AbnJpirWjk2jXMqaVeSQqqD90J8E4A b8=; b=KwcuB3dFzkcqcfVUrHenCUGCet8npmTnCtZpremQJTBL1c8SARRYCV9PR U4QrXqE+DOhNBiGoMxc84IjMYkeOXr49FwSthOPJUpkeajG0QhAQW0KmfobXf2FS 5Z++Ixpf3u9riwg2NGkrWPzYkWb76KJ/dvU8Sjisr7NRmY9UMrUjY+Fivo7TPBNA jIOxV00PbG5lEWwhujk924F8r75NROTwy6/RnQwA8sAdAB7kqj92fwEylBVomH09 XArXBRRbcp7EJjiKKins8ZFe1FmN6KNAqx/KL2XFVnoXnIt5D0OyGcIwxEgHcFFO I7FA9WiAmknayIcNOu/x2DDOo4RYw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudehgedgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveev udelueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 12 Jan 2022 02:39:05 -0500 (EST) Message-ID: <59eec9e5-f62a-4aeb-4cd6-ee5fddc2d6b4@enterprisedb.com> Date: Wed, 12 Jan 2022 08:39:03 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: Time to drop plpython2? Content-Language: en-US To: Tom Lane Cc: Andres Freund , pgsql-hackers@postgresql.org References: <20211031184548.g4sxfe47n2kyi55r@alap3.anarazel.de> <08a65981-7fec-1b9b-4061-6e3086c05914@enterprisedb.com> <3fc1211d-960b-4b2f-3e96-a6099db847fc@enterprisedb.com> <20211104195443.dystyijvufveikcp@alap3.anarazel.de> <85eb62cd-76f3-d01f-79ef-144173c16edc@enterprisedb.com> <2057149.1636943071@sss.pgh.pa.us> <20211115170632.buql3valv5mlnbni@alap3.anarazel.de> <2138217.1636996791@sss.pgh.pa.us> <20211115181246.gtnaeim6fo3vjb7c@alap3.anarazel.de> <2142324.1637000302@sss.pgh.pa.us> <21ad7747-d4de-e7b6-7864-be07929fb067@enterprisedb.com> <2594342.1641917185@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <2594342.1641917185@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 11.01.22 17:06, Tom Lane wrote: > Nonetheless, we need to make a recommendation to the > buildfarm owners about what's the minimum python3 version we intend > to support going forward. Do we want to just set it at 3.6, with > the expectation that the meson move will happen before too long? Well, the minimum supported version has always been the oldest version that actually works. I don't think we ever said, we support >= X, even though < X still actually works, about any dependency. I don't care much to tie this to Meson right now. Meson might well move to 3.8 next week and ruin this whole scheme. I'm okay with issuing some sort of recommendation for what is reasonable to test, and 3.5 or 3.6 seems like a good cutoff, considering what LTS OS currently ship. But I'm not sure if that is the same as "support".