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 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
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 wrote:
> Hi Michael,
>
> I'm not familiar enough with that area to work on it, so I submitted
> issue "PyGTKDeprecationWarning
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
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
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
