Python - plan & execution
Mon May 25 04:52:20 GMT 2020
On 27.04.2020 16:34, Jon Turney wrote:
> On 23/04/2020 22:54, Yaakov Selkowitz wrote:
>> 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:
>>> 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-* 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?
> Yes, currently it will complain about that ("install packages from
> source package '...' have non-unique current versions")
> calm is currently smart enough to exclude old soversions from that
> check, so I guess perhaps that it needs to be taught about python27 as
there will be several cases to test;
the first I am rebuilding is python-setuptools
and it seems there are half of the packages to drop in 46.4.0
python-setuptools python27-setuptools drop
python-setuptools python35-setuptools drop
python-setuptools python-setuptools-wheel drop
I expect to see other similar as all recent packages
are now only supporting 3.5 or more to 3.8
on python-setuptools-wheel, this file is not build/installed anymore
so I guess it was Py2 only
More information about the Cygwin-apps