Trelby works perfectly with the new version.
--
Gwyn Ciesla
she/her/hers
------------------------------------------------
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, January 11th, 2022 at 12:17 PM, Scott Talbert <swt(a)techie.net> wrote:
Hi all,
This is mostly targeted at maintainers (bcc'd in case not
subscribed to
Fedora devel) of packages that depend on wxPython (aka
python3-wxpython4).
TL;DR: if your package uses python3-wxpython4, please test it with
the
python3-wxpython4 from this COPR [1] and provide me any feedback,
positive
or negative, if you can.
Affected packages:
congruity
esphomeflasher (python-esphomeflasher)
grass
kicad
plater (printrun)
playonlinux
printrun-common (printrun)
pronterface (printrun)
pyhoca-gui
python3-fsleyes (python-fsleyes)
python3-fsleyes-props (python-fsleyes-props)
python3-fsleyes-widgets (python-fsleyes-widgets)
python3-fslpy (python-fslpy)
python3-humblewx (python-humblewx)
python3-matplotlib-wx (python-matplotlib)
python3-pyobd (python-pyobd)
python3-wxnatpy (python-wxnatpy)
quisk
rtlsdr-scanner
smbcmp-gui (smbcmp)
timeline
trelby
winpdb
wxGlade
wxPython 4.1.2 might be approaching release soon and I'm thinking
about
upgrading Rawhide to it when released.
A little bit of background: wxPython is the Python bindings for
wxWidgets,
the cross-platform GUI library. Currently, we have two versions of
wxWidgets packaged in Fedora:
wxGTK3 - wxWidgets 3.0.x (stable release)
wxGTK - wxWidgets 3.1.x (development release)
For wxPython, we currently have version 4.0.7 which corresponds to
wxWidgets 3.0.x release (wxGTK3). wxPython 4.1.0 (which corresponds
to
wxWidgets 3.1.x) was released in April 2020, but I have hesitated to
move
Fedora to it because it (wxPython) bundles its own copy of wxWidgets
that
didn't necessarily correspond to a released version of wxWidgets
and
having to use the bundled copy would be frowned upon in Fedora.
However,
wxPython 4.1.2 is nearing release (I think) and it seems to be locked
to
wxWidgets 3.1.5. That, plus the fact that wxPython 4.0.7 is starting
to
become harder to maintain (e.g., for Python 3.10 support), I think
it
might be time to move forward. However, wxPython 4.1.x is a fairly
major
change (mostly due to the changes in the underlying wxWidgets) so
there
could be impacts to packages that use it.
I have built this COPR [1] with a pre-release copy of wxPython 4.1.2
and
would appreciate any feedback on it. I'll try to get any bugs
addressed
ASAP. Also, please let me know if you are strongly opposed to the
change,
or if your package can't support wxPython 4.1.x.
Thanks,
Scott