Re: pygi: callback funcs and GErrors

[Laszlo Pandy <laszlok2 gmail com>]

If it crashes, it's either a wrong annotation (which should be treated
like bad code), or it's pygobject's fault. Either way it is a bug that
needs to be reported.

That bug is fixed, committed to git, and will be released in pygobject 2.28.

On Thu, Feb 24, 2011 at 8:26 AM, Christophe Saout <christophe saout de> wrote:
> Hi Laszlo,
>
> [sorry for coming back to you so late]
>
>> So if you "return False, None" from the callback, None becomes the
>> GError and it is considered set (I guess because None is a Python
>> object and not NULL).
>
> Sounds like it, I was wondering.
>
>> Then Pixbuf.save_to_callbackv() sets the GError and returns in
>> failure. There is a bug in PyGObject introspection for handling
>> cleanup of arrays when a GError is set. I've reported it, until the
>> invoke experts decide how best to solve it:
>>
>> https://bugzilla.gnome.org/show_bug.cgi?id=642708
>
> Thanks for opening a bug, I was not sure if it wasn't my fault.  There's
> been some activity on this one, plus apparantly a fix/workaround.  I'll
> have a look.
>
> Thanks a lot!
>
>        Christophe
>
>
>