From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-045.btinternet.com (mailomta9-re.btinternet.com [213.120.69.102]) by sourceware.org (Postfix) with ESMTPS id 60FC3385040C for ; Sun, 29 May 2022 15:54:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 60FC3385040C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from re-prd-rgout-005.btmx-prd.synchronoss.net ([10.2.54.8]) by re-prd-fep-045.btinternet.com with ESMTP id <20220529155437.SLXL3219.re-prd-fep-045.btinternet.com@re-prd-rgout-005.btmx-prd.synchronoss.net>; Sun, 29 May 2022 16:54:37 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 613A912425CF5496 X-Originating-IP: [86.139.167.41] X-OWM-Source-IP: 86.139.167.41 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvfedrkeeggdelfecutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceutffkvffkuffjvffgnffgvefqofdpqfgfvfenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkfffgggfufhfhffvjggtgfesthekredttdefjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepjeeukeejhffhfeffjeejkeehvefhfeefgeejheehgfevgeejfeeftdetfefhheeinecuffhomhgrihhnpehphihthhhonhdrohhrghdptgihghifihhnrdgtohhmnecukfhppeekiedrudefledrudeijedrgedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddutdehngdpihhnvghtpeekiedrudefledrudeijedrgedupdhmrghilhhfrhhomhepjhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhdpnhgspghrtghpthhtohepvddprhgtphhtthhopegthihgfihinhdqrghpphhssegthihgfihinhdrtghomhdprhgtphhtthhopehmrghrtghordgrthiivghrihesghhmrghilhdrtghomh X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.105] (86.139.167.41) by re-prd-rgout-005.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 613A912425CF5496; Sun, 29 May 2022 16:54:37 +0100 Message-ID: <0b919336-2caf-7ca1-3956-690c547ea45a@dronecode.org.uk> Date: Sun, 29 May 2022 16:54:35 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [patch] cygport : update to python 3.9 Content-Language: en-GB References: <9eb22f83-e7e9-1ec5-1aed-5e0b6c8c7848@gmail.com> From: Jon Turney To: "cygwin-apps@cygwin.com" , Marco Atzeri In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1192.4 required=5.0 tests=BAYES_00, BODY_8BITS, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2022 15:54:40 -0000 On 03/01/2022 21:42, Marco Atzeri wrote: > On 03.01.2022 18:37, Jon Turney wrote: >> On 31/12/2021 10:00, Marco Atzeri wrote: >>> Attached patch moves "default" from 3.6 to 3.9 > >>> Other point: >>> >>> As 3.5 was never really deployed, I think we can remove it from the >>> distribution. Agreed. I have started collecting a list of packages to do a purge of, and I'll add those to it. [...] > > Following is a sort of RFC, so let me know your opinion. > > Currently we have two type of Python packages > > 1) Pure python that exists at max as 2.7 3.6 3.7 3.8 3.9 plus 2 and 3 > >    in that case 2/2.7 3/3.6 are EOL; >    I stopped last year to update the 2.7 and I am thinking to do the >    same for 3.6 now. > >    I do not see the need to continue to update 3.7, it never become >    default as we jumped from 3.6 to 3.8 and it is not more >    active upstream: >    https://www.python.org/dev/peps/pep-0537/#lifespan > >    We can update the 3.8 and 3.9 while preparing/testing for 3.10 > >    source package will continue to use the "python-*" form, while >    "python3-*" should not be used. I disagree about the second half of that sentence. From a package management point of view: * being able to script 'install python3, python3-foo' and get the foo for the default python is useful * having the setup remember that python3-foo was installed (causing python39-foo to be installed), means when the default python is updated from python39 to python3nn, setup will also install python3nn-foo, so local scripts with a python3 shebang which 'import foo' continue to work. I've posted a cygport patch which adjusts cygport to generate these python3-foo virtual packages. What do you think about that? > 2) python packages derived from other packages, where the >    nomenclature is not uniform: > >    Where we have all variants >     libxml2          python27-libxml2 >     libxml2          python36-libxml2 >     libxml2          python37-libxml2 >     libxml2          python38-libxml2 > >   Only one as I moved from supporting 2 to supporting only 3 >     postgresql       postgresql-plpython > >   To hybrid version >     openbabel        python2-openbabel   (not updated anymore) >     openbabel        python38-openbabel > >   I think we should stop to call derived packages "python3-*". >   Or we use the full version as python38-openbabel or >   no version at all as python-gdal I think where the package produces a python binding for a specific python version, the package name should have that version (i.e. python3x-foo). > In general > >   We should also stop to pull as dependency "python3" >   or "python3-devel" as build dependency. >   Use the full version for dependencies. I don't think those need to appear in the BUILD_REQUIRES at all. scallywag is capable of inferring from 'inherit python*' that certain python packages are build requirements. >   Plus use "python3_fix_shebang SCRIPT" for setting the proper >   interpreter and avoid the issue seen on mercurial and dblatex >   https://cygwin.com/pipermail/cygwin/2021-December/250282.html >   I used a cruder version but python3_fix_shebang should do the work