GNOME Bugzilla – Bug 687492
GObject.signal_list_ids raises SystemError
Last modified: 2012-11-06 04:17:17 UTC
The following was found when writing tests for: bug 687487 >>> from gi.repository import GObject >>> GObject.signal_list_ids(GObject.TYPE_INVALID) SystemError: error return without exception set This should probably raise a ValueError instead but will most likely behave differently with the introspection binding.
Also happens with: GObject.signal_lookup('NOT_A_SIGNAL_NAME', GObject.TYPE_INVALID)
What does the old static bindings do? Should possibly mimic that behavior, unless it's really wrong.
(In reply to comment #2) > What does the old static bindings do? Should possibly mimic that behavior, > unless it's really wrong. This error is from the static bindings. I'm guessing the python wrapper functions are returning NULL without setting a py error, so python gives its own SystemError. This is a bug in the static bindings in regards to how they are handling the error condition. We could emulate the bug with the gi/overrides version if possible, but I think it should eventually be fixed and give a better exception/error message. The gi bindings at least raise a type error but the message text is somewhat confusing: TypeError: Must be gobject.GType, not gobject.GType
This was fixed along with bug 687487