* next python
@ 2023-03-07 4:44 Marco Atzeri
2023-03-08 21:40 ` Jon Turney
0 siblings, 1 reply; 3+ messages in thread
From: Marco Atzeri @ 2023-03-07 4:44 UTC (permalink / raw)
To: cygwin-apps
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 am also considering to not update anymore python36-* and python37-*
Any preference on both ?
Regards
Marco
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: next python
2023-03-07 4:44 next python Marco Atzeri
@ 2023-03-08 21:40 ` Jon Turney
2023-03-08 22:05 ` Marco Atzeri
0 siblings, 1 reply; 3+ messages in thread
From: Jon Turney @ 2023-03-08 21:40 UTC (permalink / raw)
To: cygwin-apps, Marco Atzeri
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.
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)
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: next python
2023-03-08 21:40 ` Jon Turney
@ 2023-03-08 22:05 ` Marco Atzeri
0 siblings, 0 replies; 3+ messages in thread
From: Marco Atzeri @ 2023-03-08 22:05 UTC (permalink / raw)
To: Jon Turney, cygwin-apps
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-03-08 22:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-07 4:44 next python Marco Atzeri
2023-03-08 21:40 ` Jon Turney
2023-03-08 22:05 ` Marco Atzeri
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).