public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin-apps@cygwin.com
Subject: Re: Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages)
Date: Mon, 1 Apr 2024 16:22:37 +0100	[thread overview]
Message-ID: <6b96f17c-d868-450a-8546-65a931395153@dronecode.org.uk> (raw)
In-Reply-To: <83c5edd8-ec93-4cb4-b862-3a6a22fa841c@dronecode.org.uk>

On 24/03/2024 17:46, Jon Turney via Cygwin-apps wrote:
> On 24/03/2024 17:31, Marco Atzeri via Cygwin-apps wrote:
>> On 24/03/2024 15:07, Jon Turney wrote:
>>> On 24/09/2023 13:32, Jon Turney via Cygwin-apps wrote:
>>>
>>> I assume you are OK with the removal of python 3.5 (EOL Sept 2020) 
>>> and 3.6 (EOL Dec 2021)?
>>>
>>> (I'm still dealing with cleaning up the final pieces of python27 
>>> detritus, but these should hopefully be much smaller tasks)
>>>
>>
>> nothing should depend from 3.5
>> not sure for 3.6
> 
> I've automated some of the analysis I was doing for python2 packages and 
> the results are now available at [1].
> 
> So yeah, it looks like nothing uses 3.5.

I've removed some 3.4 detritus, and 3.5

Perhaps you can clarify the situation with python-pip: python-pip 
19.0.3-1, 19.1.1-1 and 19.2.3-1 are not evaluated are being removable, 
despite python35-pip being not needed anymore, as that source also 
produces python-pip-wheel, which is depended upon by 
python3{6,7,8,9}-virtualenv.

A similar situation exists with python-setuptools, python35-setuptools 
and python-setuptools-wheel.

(virtualenv also depends on python-wheel-wheel, but that tracks the 
latest version)

> There are just a couple of packages using 3.6, I guess I'll ping the 
> maintainers about those.
> 
> [1] https://cygwin.com/packages/reports/python_rebuilds.html

It looks like the situation with 3.6 is a bit more complex, as some 
things have a generic python3 dependency, rather than python36 as they 
should, so that report isn't complete.

I have some tools to correct those dependencies, so the situation should 
become clearer after I run those...


  parent reply	other threads:[~2024-04-01 15:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 12:32 Bonfire of the Packages Jon Turney
2023-09-24 18:20 ` gs-cygwin.com
2023-09-24 20:13   ` Thomas Wolff
2024-03-24 14:07 ` Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages) Jon Turney
2024-03-24 17:31   ` Marco Atzeri
2024-03-24 17:46     ` Jon Turney
2024-03-24 18:51       ` Brian Inglis
2024-03-27 20:07         ` Jon Turney
2024-03-28 17:50       ` Jon Turney
2024-04-18  6:01         ` Ake Rehnman
2024-04-19 12:16           ` Jon Turney
2024-03-28 17:50       ` Jon Turney
2024-03-29 18:32         ` David Rothenberger
2024-03-30 15:25           ` Jon Turney
2024-04-01 17:16             ` David Rothenberger
2024-04-02 14:38               ` Jon Turney
2024-04-02 14:58                 ` Takashi Yano
2024-04-05 12:46                   ` Jon Turney
2024-04-05 23:17                     ` Takashi Yano
2024-04-01 15:22       ` Jon Turney [this message]
2024-03-27 21:18 Brian Inglis
2024-03-28 17:49 ` Jon Turney
2024-03-28 19:08   ` Brian Inglis

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=6b96f17c-d868-450a-8546-65a931395153@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=marco.atzeri@gmail.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).