DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7671C3840C3D
Subject: Re: Apparent bug in either (1) Cygwin default Package-list or (2)
 Package "bzr" dependency-list
To: cygwin@cygwin.com
References: <CAGUd5DUvzsGYvfj-5eT5D=_WWxQ2_gvemMOLND2_1Ht1M9jtoA@mail.gmail.com>
 <45a8baf1-f636-7c03-ec1f-7c72ee73c56d@SystematicSw.ab.ca>
 <f4e59e7b-3a69-1f56-5276-f7036a5065c6@dronecode.org.uk>
 <d25f12af-f495-fa79-c29f-aa8f0cb179d7@SystematicSw.ab.ca>
 <CAGUd5DWJ-NEZ-9Z-2tzsAptNKnwxJcJ5wTtHk2a2h-45yZTOxA@mail.gmail.com>
 <MN2PR17MB39991ED3424DF98A4703CBBFB8970@MN2PR17MB3999.namprd17.prod.outlook.com>
Message-ID: <b9b65cfe-282d-47ba-3133-9b58717c73cc@gmail.com>
Date: Mon, 22 Jun 2020 07:20:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <MN2PR17MB39991ED3424DF98A4703CBBFB8970@MN2PR17MB3999.namprd17.prod.outlook.com>
Content-Language: it
Precedence: list
From: Marco Atzeri via Cygwin <cygwin@cygwin.com>
Reply-To: Marco Atzeri <marco.atzeri@gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.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


--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple