From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: next python
Date: Wed, 8 Mar 2023 23:05:21 +0100 [thread overview]
Message-ID: <84ea4b0c-d632-48d8-c328-455f1a3528e7@gmail.com> (raw)
In-Reply-To: <d2d750f6-f078-5b00-2c98-9ba837be8403@dronecode.org.uk>
On 08.03.2023 22:40, Jon Turney wrote:
> On 07/03/2023 04:44, Marco Atzeri via Cygwin-apps wrote:
>> Hi Guys,
>>
>> I was looking to start packing 3.10.X but I noticed
>> that 3.11.2 is already out.
>>
>> Should I skip 3.10 and go directly to 3.11 ?
>
> I think that's probably the right thing to do.
thanks for confirming
>
> It takes us a long while to find the maintainer time to get all the
> modules and bindings updated, so trying to do that for both 3.10 and
> 3.11 probably isn't a good idea.
>
> (although I'm probably in a place now where I have enough automation to
> start trying to do automatic rebuilds of affected packages)
>
the major problem will be testing as on the main packages (python3X)
it stacks on some IO.
Almost all the python3X-* packages require the packages to
be installed for the test to work.
Usually I run only manually the test for 3.9 versions to save time.
>> I am also considering to not update anymore python36-* and python37-*
>
> That also seems reasonable, since 3.6 is already EOL and 3.7 is EOL in Jun.
>
Regards
Marco
prev parent reply other threads:[~2023-03-08 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 4:44 Marco Atzeri
2023-03-08 21:40 ` Jon Turney
2023-03-08 22:05 ` Marco Atzeri [this message]
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=84ea4b0c-d632-48d8-c328-455f1a3528e7@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).