[gstreamer-bugs] [Bug 617233] New: gst-python: implement statically registered plugins in Python

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=617233
  GStreamer | gst-python | git

           Summary: gst-python: implement statically registered plugins in
                    Python
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gst-python
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: lsinger at caltech.edu
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


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?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.