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 615982 - Use the stack allocation API from GObject-Introspection
Use the stack allocation API from GObject-Introspection
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: introspection
unspecified
Other Linux
: Low enhancement
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-16 18:07 UTC by Zach Goldberg
Modified: 2013-01-08 16:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Zach Goldberg 2010-04-16 18:07:51 UTC 
Stack allocation is significantly faster and avoids a whole lot of reference counting responsibility from PyGI.  We should work on converting all functions of the form

GArgType *arg_type;
arg_type = g_arg_info_get_return_type(arg_info);

to

GArgType arg_type;
g_arg_info_load_return_type(arg_info, &arg_type);
Comment 1 Will Thompson 2012-01-23 15:52:33 UTC 
For anyone looking at this here in the future, GArgType has become GITypeInfo, and GArgInfo has become GICallableInfo.
Comment 2 Martin Pitt 2012-04-24 14:03:31 UTC 
Assuming that this still applies.
Comment 3 Martin Pitt 2013-01-08 16:14:28 UTC 
Done in 
http://git.gnome.org/browse/pygobject/commit/?id=c02a00ae9599a661076630b21b7e24e78fb88c29

We still have a few _get_ methods in pygi-cache.c, as these are kept for a long time in the PyGIArgCache* structs.