From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Python - plan & execution
Date: Thu, 23 Apr 2020 17:54:47 -0400 [thread overview]
Message-ID: <03c21d5061bedff0a1be2d2fee2ecd4bd9b61362.camel@cygwin.com> (raw)
In-Reply-To: <3bc0b1e5-adb3-1824-524b-a0a2465782f7@gmail.com>
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:
> >
> > * python2-2.7.z continues to provide all '2' symlinks.
> >
> > * 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.
> >
> > * Similarly, a separate package (in Fedora it's called 'python-
> > unversioned-command') provide unversioned symlinks, pointing to 2.7 for
> > now (for compatibility).
> >
> > * Anything currently dependent on 'python' or 'python2' should either
> > be dropped if no longer needed, switched to 3 is possible, otherwise
> > rebuilt.
> >
> > * 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".
> >
> > * 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.
>
> 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=git/cygwin-packages/python3.git;a=commitdiff;h=772172be59111366ece38aebb1ea876322bfdd2f
> 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
>
> currently we have
>
> 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.
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
next prev parent reply other threads:[~2020-04-23 21:54 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 3:47 Putting packages up for adoption Yaakov Selkowitz
2020-03-20 5:04 ` Marco Atzeri
2020-03-20 6:05 ` ASSI
2020-03-20 10:19 ` Corinna Vinschen
2020-03-20 10:23 ` Corinna Vinschen
2020-03-20 8:13 ` Hamish McIntyre-Bhatty
2020-03-20 8:28 ` Marco Atzeri
2020-03-20 9:29 ` Jan Nijtmans
2020-03-20 10:22 ` Corinna Vinschen
2020-03-22 22:34 ` Yaakov Selkowitz
2020-03-23 12:07 ` Jan Nijtmans
2020-03-23 15:45 ` Yaakov Selkowitz
2020-03-23 21:04 ` Jan Nijtmans
2020-03-23 23:37 ` Yaakov Selkowitz
2020-03-24 11:41 ` Jan Nijtmans
2020-03-24 13:51 ` Yaakov Selkowitz
2020-03-24 14:11 ` Jan Nijtmans
2020-03-24 14:24 ` Yaakov Selkowitz
2020-03-24 19:27 ` Jan Nijtmans
2020-04-01 9:10 ` Jan Nijtmans
2020-03-20 10:19 ` Corinna Vinschen
2020-03-20 12:11 ` Jon Turney
2020-03-24 20:19 ` Andrew Schulman
2020-04-01 20:58 ` Yaakov Selkowitz
2020-04-02 7:35 ` Corinna Vinschen
2020-07-21 0:33 ` Andrew Schulman
2020-03-20 12:09 ` Jon Turney
2020-03-21 12:47 ` Thomas Wolff
2020-03-21 14:10 ` Jon Turney
2020-03-20 12:31 ` Marco Atzeri
2020-03-20 17:32 ` Achim Gratz
2020-03-20 19:16 ` Hamish McIntyre-Bhatty
2020-03-20 19:22 ` Yaakov Selkowitz
2020-03-20 20:30 ` Marco Atzeri
2020-03-22 15:34 ` ASSI
2020-03-22 16:36 ` ASSI
2020-03-22 19:49 ` Yaakov Selkowitz
2020-03-22 20:39 ` Achim Gratz
2020-03-22 19:03 ` Achim Gratz
2020-03-23 17:14 ` ASSI
2020-03-23 23:06 ` Marco Atzeri
2020-03-20 16:17 ` Doug Henderson
2020-03-21 14:12 ` Jon Turney
2020-03-26 5:54 ` Marco Atzeri
2020-03-26 7:19 ` Yaakov Selkowitz
2020-03-27 17:52 ` Marco Atzeri
2020-03-27 20:52 ` Yaakov Selkowitz
2020-03-28 3:33 ` Marco Atzeri
2020-03-30 6:01 ` Yaakov Selkowitz
2020-03-27 17:53 ` Marco Atzeri
2020-03-27 18:32 ` Hamish McIntyre-Bhatty
2020-03-27 19:10 ` Yaakov Selkowitz
2020-03-27 20:02 ` Hamish McIntyre-Bhatty
2020-04-10 12:52 ` Python - plan & execution Marco Atzeri
2020-04-23 21:54 ` Yaakov Selkowitz [this message]
2020-04-27 14:34 ` Jon Turney
2020-05-25 4:52 ` Marco Atzeri
2020-05-25 13:43 ` Jon Turney
2020-05-25 23:45 ` Yaakov Selkowitz
2020-05-26 4:31 ` Marco Atzeri
2020-06-08 19:20 ` Jon Turney
2020-06-08 20:02 ` Marco Atzeri
2020-06-09 13:20 ` Jon Turney
2020-06-09 19:16 ` Marco Atzeri
2020-06-12 14:44 ` Jon Turney
2020-05-25 5:02 ` Marco Atzeri
2020-07-07 18:40 ` Marco Atzeri
2020-07-09 23:52 ` airplanemath
2020-07-10 5:34 ` Marco Atzeri
2020-04-04 3:17 ` Putting packages up for adoption Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03c21d5061bedff0a1be2d2fee2ecd4bd9b61362.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).