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 617233 - gst-python: implement statically registered plugins in Python
gst-python: implement statically registered plugins in Python
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-python
git master
Other All
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-29 23:04 UTC by Leo Singer
Modified: 2012-12-17 11:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Leo Singer 2010-04-29 23:04:38 UTC
I am working on a project that is developing a lot of in-house elements.  We usually do a "rough draft" of a new element in Python, and then when it is working as we want it to we port it to C.

As I understand it, in C it is possible to register application-specific plugins, using gst_plugin_register_static, such that gst_element_factory_make, gst_parse_launch, etc. can see custom elements, but those elements don't get recorded permanently in the global plugin registry.

However, we currently lack the ability to register Pythonic element classes in static plugins because the function gst_plugin_register_static is not exposed by gst-python.  In fact when I build gst-python I see the warning:

Could not write function plugin_register_static: No ArgType for 'const-GstPluginDesc*'

Is there any plan to add this feature, or is there a technical reason that this cannot be done in gst-python?
Comment 1 Sebastian Dröge (slomo) 2012-12-17 11:38:42 UTC
Closing this bug now, gst-python is only an extension module to pygi now and this bug doesn't make much sense anymore in this context.