From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Apparent bug in either (1) Cygwin default Package-list or (2) Package "bzr" dependency-list
Date: Mon, 22 Jun 2020 07:20:10 +0200 [thread overview]
Message-ID: <b9b65cfe-282d-47ba-3133-9b58717c73cc@gmail.com> (raw)
In-Reply-To: <MN2PR17MB39991ED3424DF98A4703CBBFB8970@MN2PR17MB3999.namprd17.prod.outlook.com>
On 22.06.2020 04:21, Allen Hewes via Cygwin wrote:
>> -----Original Message-----
>> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of My Name via
>> Cygwin
>> Sent: Sunday, June 21, 2020 2:04 PM
>> To: Brian.Inglis@systematicsw.ab.ca
>> Cc: The Cygwin Mailing List <cygwin@cygwin.com>
>> Subject: Re: Apparent bug in either (1) Cygwin default Package-list or (2)
>> Package "bzr" dependency-list
>>
>> This is mostly over my head, so I'm sorry if my comment here is irrelevant,
>> but I'll point out in case anyone here doesn't know, Python 3 doesn't make
>> Python 2 obsolete. They are somewhat incompatible. Python 2 source
>> doesn't always run in Python 3 without extensive modification. If there's any
>> message you all would like me to deliver to the Bazaar (bzr) forum, I will; but
>> I'm not a Bazaar developer either, just a user.
>>
>
> Yep, I am in agreement here. I don't understand why Python 2 gets attention from Cygwin maintainers. I have a found a few packages that are "linked" (e.g. they have dependencies on either the Python27 or Python2/Python meta-package), which would explain this to some degree. Usually, it's just a rebuild (e.g. a re-configure) of the depending-ee...
>
> I can't get rid of three Python 2.7 packages: python27, python27-pip, python27-setuptools. I switched over to using alternatives (sometime ago) so that I can "stop" the craziness of the meta-package "python". I don't want Python 2 as my 'python'.
>
> The need to have two Pythons installed at the same time seems to be over. Shouldn't this remove the need to have meta-packages?
>
> Cygiwn isn't alone is keeping Python 2 alive.
>
> /allen
>
by default "python" is "python2" so anything calling python still
requires python2, see:
https://www.python.org/dev/peps/pep-0394/
and there are a lot of packages in cygwin doing it.
Packaging requires time and currently on python we are short of it.
I am moving to package all python-subpackages for 3.8 and
after we can look to move some packages from python2 (2.7)
to python 3 (target 3.8)
Regards
MArco
next prev parent reply other threads:[~2020-06-22 5:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 3:33 My Name
2020-06-19 6:55 ` Brian Inglis
2020-06-19 9:39 ` marco atzeri
2020-06-20 14:41 ` Jon Turney
2020-06-20 14:44 ` Marco Atzeri
2020-06-21 16:15 ` Brian Inglis
2020-06-21 18:04 ` My Name
2020-06-22 2:21 ` Allen Hewes
2020-06-22 2:45 ` My Name
[not found] ` <MN2PR17MB39993A62062F020FE99CA0B6B8970@MN2PR17MB3999.namprd17.prod.outlook.com>
[not found] ` <CAGUd5DW8vwBB3QtOLaTB1FhPVGB9ugx+xxo=CxCWFVB3hWFsMw@mail.gmail.com>
2020-06-22 5:26 ` Allen Hewes
2020-06-22 5:20 ` Marco Atzeri [this message]
2020-06-22 5:49 ` Allen Hewes
[not found] ` <CAGUd5DXo=Wu1jx64OkQbjHtvC_5gcaUJF6_mnL0YH=Xmhd_x6g@mail.gmail.com>
2020-06-22 6:54 ` Allen Hewes
2020-06-22 7:02 ` Allen Hewes
2020-06-24 21:34 ` Jon Turney
2020-06-25 11:53 ` Brian Inglis
2020-06-25 21:48 ` Jon Turney
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=b9b65cfe-282d-47ba-3133-9b58717c73cc@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).