From: Hamish McIntyre-Bhatty <cygwin@hamishmb.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: python2 removal
Date: Wed, 10 Apr 2024 20:19:32 +0100 [thread overview]
Message-ID: <41bb73d7-da99-4c3b-82f0-6eee6c59c53d@hamishmb.com> (raw)
In-Reply-To: <f5b6ffd7-d063-4d15-b1a9-843d52f0af4c@hamishmb.com>
On 19/01/2024 18:23, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 18/01/2024 19:40, Jon Turney wrote:
>> On 18/01/2024 19:31, Jon Turney via Cygwin-apps wrote:
>> [...]
>>>> python-wx-devel wxWidgets C++ application framework (Python
>>>> bindings)
>> [...]
>>>
>>> python-wx-devel is the last remnant of python2 bindings for wx (the
>>> python3 binding comes from a different, irregularly named source
>>> package python3-wx), so can also be removed.
>>
>> Cc:ing Hamish as a note that if/when python3-wx is updated, we should
>> see if it's now possible to rename the source package to python-wx.
>>
>> Unrelated question: Do you mind if I vault the (orphaned, last updated
>> circa 2016) wxWidgets 2.8 packages, which I assume are of very limited
>> use to anybody...
>
> Okay, I'd be happy to try renaming the package to python-wx the next
> time I update python3-wx.
>
> I'm indifferent to the wxWidgets 2.8 packages, I've never used them and
> wxWIdgets 3.0 is also pretty compatible with 2.8 from my understanding,
> so the 2.8 packages aren't needed.
>
> Hamish
>
>
I realise I forgot to ask, but how could I go about renaming python3-wx
to python-wx when I update? I also maintained python-wx, so I shouldn't
need any extra permissions I don't think.
Best,
Hamish
next prev parent reply other threads:[~2024-04-10 19:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:52 Jon Turney
2023-01-15 19:31 ` Ken Brown
2023-01-16 12:49 ` Jon Turney
2023-01-16 14:22 ` Ken Brown
2023-01-16 12:49 ` Jon Turney
2023-02-25 16:23 ` Jon Turney
2023-02-25 16:51 ` Adam Dinwoodie
2023-02-26 11:56 ` Jon Turney
2023-04-30 18:25 ` Jon Turney
2023-04-30 20:32 ` Adam Dinwoodie
2023-05-01 17:53 ` Jon Turney
2023-02-25 16:23 ` Jon Turney
[not found] ` <003a01d94a86$750f4b70$5f2de250$@samsung.com>
2023-02-27 13:36 ` Jon Turney
2023-02-25 16:23 ` Jon Turney
2023-03-07 17:27 ` Jon Turney
2023-01-17 2:27 ` David Rothenberger
2023-03-14 19:16 ` Jon Turney
2023-03-14 19:17 ` Jon Turney
2023-03-15 12:56 ` Brian Inglis
2023-03-15 16:46 ` marco atzeri
2023-03-16 13:29 ` ITA (was Re: python2 removal) Jon Turney
2023-03-16 15:53 ` ITA xlsx2csv " Brian Inglis
2023-03-16 18:57 ` Jon Turney
2023-03-16 21:12 ` Brian Inglis
2023-03-22 7:36 ` Jari Aalto
2023-03-22 16:23 ` Jon Turney
2023-04-02 15:47 ` python2 removal Jon Turney
2023-04-02 15:55 ` Jon Turney
2023-06-01 16:54 ` Jon Turney
2023-04-02 16:00 ` Jon Turney
2023-04-03 1:08 ` marco atzeri
2023-04-11 6:49 ` Marco Atzeri
2023-06-04 19:17 ` Jon Turney
2023-07-02 14:30 ` Jon Turney
2023-07-07 18:54 ` Marco Atzeri
2023-07-09 16:50 ` Jon Turney
2024-01-18 19:31 ` Jon Turney
2024-01-18 19:40 ` Jon Turney
2024-01-19 18:23 ` Hamish McIntyre-Bhatty
2024-04-10 19:19 ` Hamish McIntyre-Bhatty [this message]
2024-04-11 12:23 ` Jon Turney
2023-06-11 18:06 ` Jon Turney
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=41bb73d7-da99-4c3b-82f0-6eee6c59c53d@hamishmb.com \
--to=cygwin@hamishmb.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).