Re: Virtaal and Python warnings



Hi,

This seems to be fallout from the following change in glib:
https://bugzilla.gnome.org/show_bug.cgi?id=687659

The PyGObject ticket and commit you mentioned was to ensure PyGObject
works after the glib change. However, this fix was for PyGObject 3 or
"PyGI" which is the introspection version of the Python bindings. It
looks like Virtaal is using PyGTK and the older PyGObject 2 static
bindings. I see a back port of the fix for PyGObject 2 here:
https://bugzilla.gnome.org/show_bug.cgi?id=694108
https://git.gnome.org/browse/pygobject/commit/?h=pygobject-2-28&id=9456ba70fdb

But it is unclear if it is fully resolved based on the comments in the
ticket and it doesn't look like there has been a PyGObject 2 release
for a few years (the last tag is dated 2011-06-13 release 2.28.6).

Apart from testing and releasing a new PyGObject 2 from the
pygobject-2-28 branch. A different approach is to update the app to
PyGObject 3 and use the compatibility shim (pygtkcompat):
https://wiki.gnome.org/PyGObject/IntrospectionPorting

-Simon

On Sat, Aug 3, 2013 at 5:37 AM, Reinout van Schouwen <reinouts gnome org> wrote:
cc: gnome-i18n-list

Dear Python hackers,

We're doing a small translation sprint here at GUADEC and found out that we
couldn't use Virtaal any more, at least on the latest Sabayon and Fedora
releases. It used to work fine. Warnings are printed to the console at
startup and the editing boxes remain gray when you click on them.

$ virtaal
/usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning:
attempting to add an interface (GtkCellEditable) to class (UnitView) after
class_init
  type_register(cls, namespace.get('__gtype_name__'))
/usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning:
attempting to add an interface (GtkCellEditable) to class (CellWidget) after
class_init
  type_register(cls, namespace.get('__gtype_name__'))
Traceback (most recent call last):
  File
"/usr/lib/python2.7/site-packages/virtaal/views/widgets/storecellrenderer.py",
line 192, in do_start_editing
    self._editor_editing_done_id = editor.connect("editing-done",
self._on_editor_done)
TypeError: <UnitView object at 0x18f4fa0 (UnitView at 0x16ae570)>: unknown
signal name: editing-done

Corresponding bug reports are:
http://bugs.locamotion.org/show_bug.cgi?id=2713
https://bugzilla.redhat.com/show_bug.cgi?id=988049

After some research we found that the problem could be related to
https://bugzilla.gnome.org/show_bug.cgi?id=686149 and this commit:
https://git.gnome.org/browse/pygobject/commit/?h=pygobject-3-8&id=efcb0f9fda65e24ae98438d61487d06db9eac1b1

Could you shed some light into the darkness for us? We've tried to debug the
problem but the error is a bit to deep for our feeble translator minds. ;)

--
Reinout van Schouwen
_______________________________________________
python-hackers-list mailing list
python-hackers-list gnome org
https://mail.gnome.org/mailman/listinfo/python-hackers-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]