From: Allen Hewes <allen@decisiv.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: missing Python 3.7 for python3 package version
Date: Mon, 27 Jul 2020 16:02:17 +0000 [thread overview]
Message-ID: <MN2PR17MB3999CCCD53E5E04E03520291B8720@MN2PR17MB3999.namprd17.prod.outlook.com> (raw)
In-Reply-To: <7c403043-c276-bce9-73e4-7fc67ad017fa@gmail.com>
>
>
> 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.
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.
Why can't Cygwin pick one Python horse and ride it now that Python 2.7 is gone?
/allen
________________________________
Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.
next prev parent reply other threads:[~2020-07-27 16:02 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 [this message]
2020-07-28 7:09 ` Marco Atzeri
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=MN2PR17MB3999CCCD53E5E04E03520291B8720@MN2PR17MB3999.namprd17.prod.outlook.com \
--to=allen@decisiv.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).