From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [patch] cygport : update to python 3.9
Date: Wed, 29 Jun 2022 17:46:26 +0200 [thread overview]
Message-ID: <28594b1c-0968-12c1-efb2-7d7b0d2a5cca@gmail.com> (raw)
In-Reply-To: <10e94aa2-3b44-5d57-e645-94b24d981e16@hamishmb.com>
On 29.06.2022 17:36, Hamish McIntyre-Bhatty wrote:
> On 31/12/2021 10:00, Marco Atzeri wrote:
>> Attached patch moves "default" from 3.6 to 3.9
>>
>> Additional changes:
>> Remove 3.5 from all
>> Change future to 3.10
>>
>>
>> Other point:
>>
>> As 3.5 was never reall deployed, I think we can remove it from the
>> distibution.
>>
>> As we have a lot of python3-* is obsoleded py python36-*
>> what is the best way to updated to python39-* when available ?
>>
>> Regards
>> Marco
>>
>>
>>
>>
>
> Just noticed this. I'll update my packages to rebuild against Python 3.10.
We have not yet 3.10.
I was planning to deply it in July
>
> I'm also going to try to get wxWidgets 3.1 (and thus newer wxPython)
> working again soon, but I might need some help debugging the test suite
> if it still misbehaves.
>
> I guess that means I'm now building wxWidgets and wxPython for 4
> different versions of Python on 64-bit and 32-bit. I'll be glad when
> 32-bit builds go away, it takes so long to do these builds, even on a
> Ryzen 3600.
Imagine building on a Laptop with i5-8250U CPU @ 1.60GHz
;-)
All fork intensive builds are a nightmare ..
> Hamish
Regards
MArco
next prev parent reply other threads:[~2022-06-29 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 10:00 Marco Atzeri
2022-01-03 17:37 ` Jon Turney
2022-01-03 21:42 ` Marco Atzeri
2022-05-29 15:54 ` Jon Turney
2022-07-03 12:22 ` Jon Turney
2022-07-03 12:47 ` Marco Atzeri
2022-01-04 16:05 ` Marco Atzeri
2022-01-08 16:32 ` Jon Turney
2022-01-08 17:12 ` Marco Atzeri
2022-06-29 15:36 ` Hamish McIntyre-Bhatty
2022-06-29 15:46 ` Marco Atzeri [this message]
2022-06-29 15:51 ` Hamish McIntyre-Bhatty
2022-06-29 18:35 ` Hamish McIntyre-Bhatty
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=28594b1c-0968-12c1-efb2-7d7b0d2a5cca@gmail.com \
--to=marco.atzeri@gmail.com \
--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).