On 19/01/2021 18:36, Marco Atzeri via Cygwin-apps wrote:
> On 19.01.2021 19:11, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 18/01/2021 18:39, Marco Atzeri via Cygwin-apps wrote:
>>> On 18.01.2021 18:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
Hi all,
In the
On 19.01.2021 19:11, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
On 18/01/2021 18:39, Marco Atzeri via Cygwin-apps wrote:
On 18.01.2021 18:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
Hi all,
In the (hopefully!) near future I plan to package python3-wx (aka
wxPython) version 4.1.1.
On 18/01/2021 18:39, Marco Atzeri via Cygwin-apps wrote:
> On 18.01.2021 18:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Hi all,
>>
>> In the (hopefully!) near future I plan to package python3-wx (aka
>> wxPython) version 4.1.1. This is a backwards-incompatible change with
>> wxPython
On 18.01.2021 18:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
Hi all,
In the (hopefully!) near future I plan to package python3-wx (aka
wxPython) version 4.1.1. This is a backwards-incompatible change with
wxPython 4.0.x, so I was wondering if there was a way to retain
python3-wx 4.0.x and
Hi all,
In the (hopefully!) near future I plan to package python3-wx (aka
wxPython) version 4.1.1. This is a backwards-incompatible change with
wxPython 4.0.x, so I was wondering if there was a way to retain
python3-wx 4.0.x and its binary packages in the repos after I do this
update?
Hamish