After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 637165 - Use g_vfunc_info_invoke for chaining up in vfuncs
Use g_vfunc_info_invoke for chaining up in vfuncs
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: introspection
unspecified
Other All
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on: 637145
Blocks:
 
 
Reported: 2010-12-13 17:04 UTC by Tomeu Vizoso
Modified: 2011-01-17 14:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Use g_vfunc_info_invoke for chaining up in vfuncs (9.75 KB, patch)
2010-12-13 17:04 UTC, Tomeu Vizoso 		committed Details | Review

Description Tomeu Vizoso 2010-12-13 17:04:46 UTC 
.
Comment 1 Tomeu Vizoso 2010-12-13 17:04:48 UTC 
Created attachment 176348 [details] [review]
Use g_vfunc_info_invoke for chaining up in vfuncs
Comment 2 Paolo Borelli 2010-12-18 14:02:06 UTC 
I am not familiar with pygi internals, so you probably have a better understanding then I do, however instead of having if/else in the implementation, shouldn't we just reflect the same api exposed in in GI in the pygi wrapper? In other words, maybe we should have a _wrap_g_vfunc_info_invoke instead of special casing inside the implementation of _wrap_g_function_info_invoke
Comment 3 Tomeu Vizoso 2011-01-17 14:40:33 UTC 
Attachment 176348 [details] pushed as da50d56 - Use g_vfunc_info_invoke for chaining up in vfuncs