From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) by sourceware.org (Postfix) with ESMTP id 0DBD23851C05 for ; Mon, 25 May 2020 23:45:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0DBD23851C05 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=yselkowitz@cygwin.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-257-HJWqmjx-P2OA8d7gtvR6sw-1; Mon, 25 May 2020 19:45:15 -0400 X-MC-Unique: HJWqmjx-P2OA8d7gtvR6sw-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 662A9107ACCA for ; Mon, 25 May 2020 23:45:14 +0000 (UTC) Received: from ovpn-112-96.rdu2.redhat.com (ovpn-112-96.rdu2.redhat.com [10.10.112.96]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0FDC35C1BB for ; Mon, 25 May 2020 23:45:13 +0000 (UTC) Message-ID: Subject: Re: Python - plan & execution From: Yaakov Selkowitz To: cygwin-apps@cygwin.com Date: Mon, 25 May 2020 19:45:12 -0400 In-Reply-To: <03bca51c-9f2e-bd5d-cc93-1935589c6ca3@gmail.com> References: <8de4bc18-86d2-4f3b-e2c4-8d1cd5792a23@gmail.com> <3bc0b1e5-adb3-1824-524b-a0a2465782f7@gmail.com> <03c21d5061bedff0a1be2d2fee2ecd4bd9b61362.camel@cygwin.com> <828c5f93-d70d-1028-a8f3-8249d2c47197@dronecode.org.uk> <03bca51c-9f2e-bd5d-cc93-1935589c6ca3@gmail.com> User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.6 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: Mon, 25 May 2020 23:45:19 -0000 On Mon, 2020-05-25 at 06:52 +0200, Marco Atzeri via Cygwin-apps wrote: > On 27.04.2020 16:34, Jon Turney wrote: > > On 23/04/2020 22:54, Yaakov Selkowitz wrote: > > > On Fri, 2020-04-10 at 14:52 +0200, Marco Atzeri via Cygwin-apps wrote= : > > > > Am 26.03.2020 um 08:19 schrieb Yaakov Selkowitz: > > > > > On Thu, 2020-03-26 at 06:54 +0100, Marco Atzeri via Cygwin-apps w= rote: > > > > > > Am 20.03.2020 um 04:47 schrieb Yaakov Selkowitz: > > > >=20 > > > > currently we have > > > >=20 > > > > 119 *python27* > > >=20 > > > These are fine as is, but they also don't need to be rebuilt or updat= ed > > > any more. > > >=20 > > > > 114 *python36* > > > > 115 *python37* > > > > 10 *python38* > > >=20 > > > We don't need to _obsolete or remove python3[67]-* packages, we just > > > need to track how many don't have python38-* equivalents yet. > > > Obviously that's still the vast majority, since 3.8 just got updated = to > > > a stable version. > > >=20 > > > Jon Turney, if a python-foo source package was previously building e.= g. > > > python27-foo, python36-foo, and python37-foo, and now starts building > > > only python37-foo and python38-foo, is calm going to complain? > >=20 > > Yes, currently it will complain about that ("install packages from=20 > > source package '...' have non-unique current versions") > >=20 > > calm is currently smart enough to exclude old soversions from that=20 > > check, so I guess perhaps that it needs to be taught about python27 as= =20 > > well. > >=20 >=20 > there will be several cases to test; > the first I am rebuilding is python-setuptools > and it seems there are half of the packages to drop in 46.4.0 >=20 >=20 > python-setuptools=09python27-setuptools drop I'd like to suggest you make two updates to setuptools, one to the last version which supports 2.7 with all Pythons enabled, and then to the latest version, dropping 2.7. > python-setuptools=09python35-setuptools drop 3.5 is still supported upstream and by latest setuptools, why drop this? > python-setuptools=09python36-setuptools > python-setuptools=09python37-setuptools > python-setuptools=09python38-setuptools No change here, as expected. > python-setuptools=09python-setuptools-wheel drop >=20 > on python-setuptools-wheel, this file is not build/installed anymore >=20 > usr/share/python-wheels/setuptools-41.2.0-py2.py3-none-any.whl >=20 > so I guess it was Py2 only No; since setuptools dropped Py2 support, they must have stopped declaring 'universal' compatibility, so the wheel would now be just 'py3' instead of 'py2.py3'. You don't want to drop this package, because it is used by (patched) python3Y venv as well as by python3Y- virtualenv. OTOH, since the latest setuptools won't work with python27, then python27 and python27-virtualenv shouldn't use python-setuptools-wheel anymore. I'd have to look further into the best way to handle that. -- Yaakov