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 1q8cVh-0005vy-EE for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Jun 2023 08:02:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q8cVf-0006vV-1y for pgadmin-hackers@arkaria.postgresql.org; Mon, 12 Jun 2023 08:02:43 +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 1q8cVe-0006vG-EK for pgadmin-hackers@lists.postgresql.org; Mon, 12 Jun 2023 08:02:42 +0000 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q8cVV-001sdo-Lr for pgadmin-hackers@postgresql.org; Mon, 12 Jun 2023 08:02:41 +0000 Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-9745baf7c13so590977266b.1 for ; Mon, 12 Jun 2023 01:02:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1686556953; x=1689148953; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/j1x3BkHV4JzcBDpkwE7ueYbtcc55HzR6SogfLd8434=; b=M4IpRQkcRO6BNPxmGakB2MDLN/ZyUni7ronbkqeC7jiGMgADVcGFvUB4cUe6BcIL1W I3plnrFEq/MSmIFy481KNUt9EobObBAp1BJzB+cD+i3M7WNmmQ7rsNk12dkJjo8gzZDn WMw/mhY/5rE6pr7iyAbvjSMY9UGx1CIoyvhQ3Y+JSeNqsuXH66imnAD3CGO6KVwdNpjl hmecVznJjhYaVqD6psByHFNTNtYsoM/aXCyMYFpLFUnfzigZ/2QaFYYWO9GCd9RdhvYH CW96mwMmqOpbTIehrscM2Q6GSd+k2VQgfDwa0q1HBo2E7dZSWKyP2td+iQdzoU/caQrs PRAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686556953; x=1689148953; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/j1x3BkHV4JzcBDpkwE7ueYbtcc55HzR6SogfLd8434=; b=LZre4nmz/VT/qOvj17sdEkPhy9oxQGSm15LSt1TNEoZeQe8zT0GFS1eNziYVdGfzoD CI6AE20LEPDOS+3n6sZLjkOl/iTjW6PB37bu/9w76Jk1woBYCMqJKIo1Hycn8eQuS4BM 6Rex7W5caTPw2eII4qUuGr+43lS95YOqTKlGEFz9masGwvSJPBua2KuRsX/olyzu9T9D vFlFJ2qO4KNeysuq5kbCIlIzPEEGzHQnhh1AMEoS1zGtk22pnI1wyxiU9l6+OnuMPLjN 4ttTc32btbC1tZqhrakeMpA8TM2vXWOElmxVv2S4u5fvpu7gMzFMJ84Y6eGlx2uVpxF9 nkBQ== X-Gm-Message-State: AC+VfDx8UH5/NfJ3405n5xD/pUA2DL3C83WiQmjLw5LBaGy1w6ev3gBU 44mrPJjdvmZBrlz7ytELpA8Oblil23D/ACbIjry5qckpTQsNP27EBO4= X-Google-Smtp-Source: ACHHUZ5+TF0v4vcI3u+Ccu8vcZ+mhXNVvdzbtvgFIf0PBFAm2OyT7a4Ls/g5oWayti/aC08lMDzG2EdC70N2KfysWFw= X-Received: by 2002:a17:907:1626:b0:977:95f4:5cca with SMTP id hb38-20020a170907162600b0097795f45ccamr8546862ejc.54.1686556952537; Mon, 12 Jun 2023 01:02:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Mon, 12 Jun 2023 09:02:21 +0100 Message-ID: Subject: Re: Drop support for Python 3.7? To: Aditya Toshniwal Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000000cbe6505fdea24ca" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000cbe6505fdea24ca Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 12 Jun 2023 at 07:55, Aditya Toshniwal < aditya.toshniwal@enterprisedb.com> wrote: > Hi Dave, > > On Fri, Jun 9, 2023 at 7:04=E2=80=AFPM Dave Page wrot= e: > >> >> >> On Fri, 9 Jun 2023 at 14:23, Aditya Toshniwal < >> aditya.toshniwal@enterprisedb.com> wrote: >> >>> Hi Hackers, >>> >>> Beginning Flask v2.3.0, the support for Python 3.7 is dropped. So we >>> have pinned to the last version of 2.2.*. >>> We cannot stay there, and we'll need to update this. Most of the python >>> packages are dropping support for python 3.7. >>> So should we move ahead or stay put? I can see most OS's have at least >>> python 3.8 packages. >>> >> >> Most? What platforms do we support that don't have 3.8+? >> > From what we support, only Debian 10(Buster) do not have a 3.8+ python > release. > Hmm, well Buster has just moved into LTS, where it'll be for about another year. I'm on the fence about whether we should de-support it now; it's still in common use AFAIA - in fact postgresql.org still has a handful of installations that have yet to be moved to Bullseye. --=20 Dave Page Blog: https://pgsnake.blogspot.com Twitter: @pgsnake EDB: https://www.enterprisedb.com --0000000000000cbe6505fdea24ca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, 12 Jun 2023 at 07:55, Aditya = Toshniwal <aditya.t= oshniwal@enterprisedb.com> wrote:
Hi= =C2=A0Dave,

On Fri, Jun 9, 2023 at 7:04=E2=80=AFPM Dave Page <dpage@pgadmin.org>= wrote:


On = Fri, 9 Jun 2023 at 14:23, Aditya Toshniwal <aditya.toshniwal@enterprisedb.co= m> wrote:
Hi=C2=A0Hackers,

Beginning=C2=A0Flask v2.3.0, the support for Python = 3.7 is dropped. So we have pinned to the last version of 2.2.*.
We cannot stay there, and we'll= need to update this. Most of the python packages are dropping support for = python 3.7.
So should we= move ahead or stay put? I can see most OS's have at least python 3.8 p= ackages.

Most? What platforms d= o we support that don't have 3.8+?=C2=A0
=
=C2=A0do not have a 3.8+ py= thon release.

Hmm,= well Buster has just moved into LTS, where it'll be for about another = year. I'm on the fence about whether we should de-support it now; it= 9;s still in common use AFAIA - in fact p= ostgresql.org still has a handful of installations that have yet to be = moved to Bullseye.

--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

ED= B: https://www.e= nterprisedb.com

--0000000000000cbe6505fdea24ca--