From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Python 3.9
Date: Mon, 13 Dec 2021 11:52:45 +0000 [thread overview]
Message-ID: <DB3PR0202MB35616F9812F782B048BEE27FE7749@DB3PR0202MB3561.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <026dad51-b7ec-dd12-efd8-93dce1b55057@gmail.com>
On 12/12/2021 22:14, Marco Atzeri wrote:
> On 09.12.2021 07:26, Marco Atzeri wrote:
>> After the latest update of python 3.6-3.8 I have started the
>> deployment of python39
>>
>> I will send the Announcement when I will be a bit more in depth
>> on the deployment of the python39-* packages
>>
>>
>> $ cygcheck -cd |grep python39 |wc -l
>> 25
>>
>> $ cygcheck -cd |grep python38 |wc -l
>> 154
>>
>> It could take a while..
>>
>
>
> $ cygcheck -cd |grep python39 |wc -l
> 44
>
> but I hit a missing package: python-imaging
>
>
> Hamish,
> can you upload a new python-imaging that includes the 39 ?
>
> I just uploaded the python39-olefile that seems the only dependency.
> If you need anything else let me know
>
> Regards
> Marco
Okay.
Guess I'll rebuild wxPython as well then.
I'm midway through doing an update to wxPython 4.1.x but can't get the
wxWidgets unit tests to build, so I'll do that later I guess.
Hamish
next prev parent reply other threads:[~2021-12-13 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 6:26 Marco Atzeri
2021-12-12 22:14 ` Marco Atzeri
2021-12-13 11:52 ` Hamish McIntyre-Bhatty [this message]
2021-12-13 12:32 ` Hamish McIntyre-Bhatty
2021-12-13 18:29 ` Marco Atzeri
2021-12-17 18:34 ` Hamish McIntyre-Bhatty
2021-12-17 18:35 ` Hamish McIntyre-Bhatty
2021-12-25 7:19 ` Marco Atzeri
2021-12-26 23:14 ` Hamish McIntyre-Bhatty
2021-12-28 7:17 ` Marco Atzeri
2021-12-28 10:12 ` Hamish McIntyre-Bhatty
2021-12-31 11:45 ` Marco Atzeri
2022-01-02 14:04 ` Hamish McIntyre-Bhatty
2022-01-02 16:00 ` Marco Atzeri
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=DB3PR0202MB35616F9812F782B048BEE27FE7749@DB3PR0202MB3561.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.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).