From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) by sourceware.org (Postfix) with ESMTP id 0377F3959C26 for ; Thu, 23 Apr 2020 21:54:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0377F3959C26 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-100-J_dY50RhMRGmpKvHQ5dkHQ-1; Thu, 23 Apr 2020 17:54:49 -0400 X-MC-Unique: J_dY50RhMRGmpKvHQ5dkHQ-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EA877100A614 for ; Thu, 23 Apr 2020 21:54:48 +0000 (UTC) Received: from ovpn-117-23.rdu2.redhat.com (ovpn-117-23.rdu2.redhat.com [10.10.117.23]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9427E6084D for ; Thu, 23 Apr 2020 21:54:48 +0000 (UTC) Message-ID: <03c21d5061bedff0a1be2d2fee2ecd4bd9b61362.camel@cygwin.com> Subject: Re: Python - plan & execution From: Yaakov Selkowitz To: cygwin-apps@cygwin.com Date: Thu, 23 Apr 2020 17:54:47 -0400 In-Reply-To: <3bc0b1e5-adb3-1824-524b-a0a2465782f7@gmail.com> References: <8de4bc18-86d2-4f3b-e2c4-8d1cd5792a23@gmail.com> <3bc0b1e5-adb3-1824-524b-a0a2465782f7@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.13 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=-7.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, 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-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2020 21:54:53 -0000 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 wrote: > > > Am 20.03.2020 um 04:47 schrieb Yaakov Selkowitz: > > I would suggest the following: > >=20 > > * python2-2.7.z continues to provide all '2' symlinks. > >=20 > > * python38 be updated to 3.8.2, and 3.8 be designated the next default > > 'python3' version (with the '3' symlinks continued to be kept > > separate), and adjust python-wheel.cygclass accordingly. > >=20 > > * Similarly, a separate package (in Fedora it's called 'python- > > unversioned-command') provide unversioned symlinks, pointing to 2.7 for > > now (for compatibility). > >=20 > > * Anything currently dependent on 'python' or 'python2' should either > > be dropped if no longer needed, switched to 3 is possible, otherwise > > rebuilt. > >=20 > > * Drop 2.7 from the "default" version set in python-wheel.cygclass, and > > only build those modules that are actually needed by other things by > > specifying "all". > >=20 > > * Once that's done, look at what's still depending on /usr/bin/python > > ('python-unversioned-command'), and based on that decide when that can > > be changed to point to python3. >=20 > first steps done: > - updated 3.8 to 3.8.2 > - updated 3.7 to 3.7.7 > - updated also their python doc > - upload of all of them is in progress Didn't think of it earlier, but how about updating python3 (the major- version symlinks) to 3.8 as a test: release now? That should help maintainers start the move without breaking the world for everybody else. Posted this to a branch to help: https://cygwin.com/git-cygwin-packages/?p=3Dgit/cygwin-packages/python3.git= ;a=3Dcommitdiff;h=3D772172be59111366ece38aebb1ea876322bfdd2f > next steps: > - I assume we can drop 3.5 Your call, it's still supported upstream for almost 5 more months. I wouldn't build anything python35-* except for setuptools/pip/wheel/virtualenv. > - for the time being no need to update 2.7 and 3.6 > (we are just one version behind) There's now a 2.7.18, we should probably pick that up, as it has the final upstream fixes. After that, it's time to start moving to 3.8 en masse. > - verify which python packages we need to build/rebuild >=20 > currently we have >=20 > 119 *python27* These are fine as is, but they also don't need to be rebuilt or updated any more. > 114 *python36* > 115 *python37* > 10 *python38* We don't need to _obsolete or remove python3[67]-* packages, we just need to track how many don't have python38-* equivalents yet.=20 Obviously that's still the vast majority, since 3.8 just got updated to a stable version. 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? > and ~ 225 other *python* packages (plus 10 for python35) There are a lot of _obsolete python-*, python2-*, and python3-* "packages" which we don't need to count. How many of those names are NOT _obsolete? > - verify the fedora python-unversioned-command This is the last step. -- Yaakov