HI Barrry - GRC uses PyGTK (version 3, to be specific). We use PyQt5 as
well as C++ Qt5 for the blocks. Hence when starting up GRC, you'll see GTK
warnings (and errors sometimes), but they don't seem to be harmful (at
least for now). - MLD

On Tue, Sep 24, 2019 at 10:30 PM Barry Duggan <ba...@dcsmail.net> wrote:

> Hi Michael,
>
> Looking at the subject line in my Inbox, it just struck me as strange:
> the warning is for PyGTK, and I thought we were using PyQt5. Is that
> part of the problem?
>
> ---
> Barry Duggan
>
>
> On 2019-09-24 14:53, Michael Dickens wrote:
> > Sounds good, Barry. I'll check out that issue once I see it come
> > through &
> > see if I can add anything useful to it. - MLD
> >
> > On Tue, Sep 24, 2019 at 2:20 PM Barry Duggan <ba...@dcsmail.net> wrote:
> >
> >> Hi Michael,
> >>
> >> I'm not familiar enough with that area to work on it, so I submitted
> >> issue "PyGTKDeprecationWarning #2813"
> >>
> >> ---
> >> Barry Duggan
> >>
> >>
> >> On 2019-09-24 10:09, Michael Dickens wrote:
> >> > Hi Barry - Short answer: probably yes, should be fixed. Longer answer:
> >> > The
> >> > likelihood and difficulty of fixing deprecated API depends mostly on
> >> > whether we can cleanly switch to the new API, or if we have to add in
> >> > some
> >> > "if" version checking logic to use the old API or new API. If we can
> >> > cleanly do so, then YES PLEASE let's do it! If the solution isn't
> clean
> >> > then it's worth opening a GR issue noting what's going on & why it's
> >> > not a
> >> > clean change & then we can get back to it in the future ... once maybe
> >> > it
> >> > will be a clean change. If you have the bandwidth right now to figure
> >> > out
> >> > what's going on, that would be great! Otherwise, I'd advise you to
> open
> >> > a
> >> > GR issue and provide what info you can there. Hope this is useful! -
> >> > MLD
> >> >
> >> > On Fri, Sep 20, 2019 at 9:10 PM Barry Duggan <ba...@dcsmail.net>
> wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> When I load a new Embedded Python Block in a flowgraph, I get the
> >> >> following warnings. This is before I have made any changes to the
> >> >> code.
> >> >> GR 3.8-maint, GRC 3.9.
> >> >>
> >> >> ```
> >> >>
> /usr/local/lib/python3.7/dist-packages/gnuradio/grc/gui/Dialogs.py:362:
> >> >> PyGTKDeprecationWarning: Using positional arguments with the GObject
> >> >> constructor has been deprecated. Please specify keyword(s) for
> "title,
> >> >> parent, action, buttons" or use a class specific constructor. See:
> >> >> https://wiki.gnome.org/PyGObject/InitializerDeprecations
> >> >>    transient_for=parent
> >> >>
> /usr/local/lib/python3.7/dist-packages/gnuradio/grc/gui/Dialogs.py:362:
> >> >> PyGTKDeprecationWarning: The "buttons" argument must be a
> >> >> Gtk.ButtonsType enum value. Please use the "add_buttons" method for
> >> >> adding buttons. See:
> >> >> https://wiki.gnome.org/PyGObject/InitializerDeprecations
> >> >>    transient_for=parent
> >> >> /usr/lib/python3/dist-packages/gi/overrides/Gtk.py:571:
> >> >> PyGTKDeprecationWarning: The keyword(s) "parent" have been deprecated
> >> >> in
> >> >> favor of "transient_for" respectively. See:
> >> >> https://wiki.gnome.org/PyGObject/InitializerDeprecations
> >> >>    self._init(*args, **new_kwargs)
> >> >> ```
> >> >>
> >> >> Is this something that needs to be fixed?
> >> >>
> >> >> --
> >> >> Barry Duggan
> >> >>
> >> >> _______________________________________________
> >> >> Discuss-gnuradio mailing list
> >> >> Discuss-gnuradio@gnu.org
> >> >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >> >>
> >> >
> >> >
> >> > --
> >> > Michael Dickens, Mac OS X Programmer
> >> >
> >> > Ettus Research Technical Support
> >> >
> >> > Email: supp...@ettus.com
> >> >
> >> > Web: http://www.ettus.com
> >>
> >
> >
> > --
> > Michael Dickens, Mac OS X Programmer
> >
> > Ettus Research Technical Support
> >
> > Email: supp...@ettus.com
> >
> > Web: http://www.ettus.com
>


-- 
Michael Dickens, Mac OS X Programmer

Ettus Research Technical Support

Email: supp...@ettus.com

Web: http://www.ettus.com
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to