On Sat, Dec 28, 2019 at 04:04:30PM +0100, Axel Beckert wrote:
> Control: forcemerge 946380 -1
> Control: tag -1 + confirmed
>
> Simon McVittie wrote:
> > The Python 3 version of wicd-gtk in experimental doesn't seem to have
> > any dependency that would pull in GTK, which seems unlikely to be valid
> > for a GTK GUI.
>
> This is #946380. Merging.
>
> > A GTK 3 app using PyGI would normally have to depend on both python3-gi and
> > gir1.2-gtk-3.0, which are the necessary packages to be able to use this
> > import sequence:
> >
> > #!/usr/bin/python3
> > import gi
> > gi.require_version('Gtk', '3.0')
> > from gi.repository import Gtk
> >
> > ... use Gtk.Application, Gtk.Window, etc. ...
> >
> > However, looking at the source code on sources.debian.org, it seems that
> > wicd-gtk in experimental is still using
> >
> > import gtk
> >
> > which was correct for PyGTK 2, but will not work with PyGI / GTK 3, which
> > are the only available GTK binding for Python 3.
> >
> > src/d-feet.in in the d-feet source package is a typical example of
> > a correct PyGI / GTK 3 import sequence. gnome-tweaks is another good
> > example of a relatively small and simple PyGI / GTK 3 app, while sonata
> > and reportbug might be useful as examples of legacy PyGTK 2 applications
> > that were ported to PyGI / GTK 3.
>
> Thanks for these hints!
Hi,
has there been further development? The removal of pygtk is now fairly close.
Given that there's been some movement wrt PyGI/gtk3, we can ask to force
the removal despite wicd still being around (but wicd-gtk would be rendered
uninstallable).
Cheers,
Moritz
