From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: missing Python 3.7 for python3 package version
Date: Tue, 28 Jul 2020 09:09:07 +0200 [thread overview]
Message-ID: <3a92663d-093e-3422-67f4-10ceeb2734dd@gmail.com> (raw)
In-Reply-To: <MN2PR17MB3999CCCD53E5E04E03520291B8720@MN2PR17MB3999.namprd17.prod.outlook.com>
On 27.07.2020 18:02, Allen Hewes via Cygwin wrote:
>>
>>
>> Question: any reason to not use python 3.8 ?
>>
>
> For me, it's because when you moved to 3.8 from 3.6, a "core" (popular?) number of python38-* packages weren't moved to 3.8 either. I didn't want 3 Pythons installed b/c of the move to 3.8. And I didn't want to add to the packages (the handful of python37-* I use) I build/maintain myself for my Cygwin installs.
move is in progress. Around a third of packages are already in place.
Anything you are particularly missing ?
> Currently, I have to change Setup for those Python packages for 3.8 I don't want upgraded/installed. It's an annoyance but it is what it is.
same on other distri.
Debian seems to provide 3.5, 3.7 and 3.8 plus starting with 3.9
>
> Why can't Cygwin pick one Python horse and ride it now that Python 2.7 is gone?
current horse is 3.6, next horse is 3.8
In the meantime we are also changing rider as the most expert
is not anymore available
https://sourceware.org/pipermail/cygwin-apps/2020-March/039878.html
>
> /allen
>
Regards
Marco
next prev parent reply other threads:[~2020-07-28 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 4:47 Sharuzzaman Ahmat Raslan
2020-07-27 6:02 ` Marco Atzeri
2020-07-27 6:39 ` Sharuzzaman Ahmat Raslan
2020-07-27 16:02 ` Allen Hewes
2020-07-28 7:09 ` Marco Atzeri [this message]
2020-07-28 20:17 ` Allen Hewes
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=3a92663d-093e-3422-67f4-10ceeb2734dd@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).