From: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin-apps@cygwin.com
Subject: Re: Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages)
Date: Sun, 24 Mar 2024 17:46:00 +0000 [thread overview]
Message-ID: <83c5edd8-ec93-4cb4-b862-3a6a22fa841c@dronecode.org.uk> (raw)
In-Reply-To: <696ef795-52d7-4739-9302-d5e6a7c49bf9@gmail.com>
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.
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
next prev parent reply other threads:[~2024-03-24 17:46 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 [this message]
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
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=83c5edd8-ec93-4cb4-b862-3a6a22fa841c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).