[gstreamer-bugs] [Bug 329075] New: __gsignals__ doesn' t work in classes derived from gst.Pipeline

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=329075
 GStreamer | gst-python | Ver: HEAD CVS

           Summary: __gsignals__ doesn' t work in classes derived from
                    gst.Pipeline
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-python
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: soto at informatik.uni-kl.de
         QAContact: johan at gnome.org
     GNOME version: 2.13/2.14
   GNOME milestone: Unspecified


Please describe the problem:
Hi!,

I was trying to use the __gsignals__ class attribute to define some signals of
my own in a Python class derived from gst.Pipeline, but connecting or emitting
the signal fails with an 'unknown signal' error. Using __gsignals__ with
classes
derived directly from gobject.GObject or, say, from one of the GTK classes,
works properly.

Steps to reproduce:
1. Run the attached pygst-signals.py

Actual results:
This is the output I get from pygst-signals.py:

masoft:~/Desktop/Projects/seamless-devel$ python pygst-gsignals.py
Signal emitted on object '<MyGObject object (__main__+MyGObject) at
0xb70295f4>'Signal emitted on object '<MyLabel object (__main__+MyLabel) at
0xb702961c>'
Traceback (most recent call last):
  File "pygst-gsignals.py", line 54, in ?
    p.connect('my-signal', handler)
TypeError: <MyPipeline object (pipeline0) at 0xb7029644>: unknown signal name:
my-signal

Expected results:
I would expect the exception at the end not to happen.

Does this happen every time?
Yes

Other information:


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