[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] PyQt4: PyObject in SIGNAL
From:       Giovanni Bajo <rasky () develer ! com>
Date:       2006-12-01 13:00:31
Message-ID: 4570276F.2040806 () develer ! com
[Download RAW message or body]

Mark Summerfield wrote:

>>>> what's the meaning of the string "PyObject" used within the signature of
>>>> a signal in PyQt4? I can't seem to find it in the PyQt4 documentation.
>>>> If I pass it a random python object I get core dumps and random crashes,
>>>> so I assume it's not really meant for that...
>>> You can do Python-Python signals which Phil calls "short-circuit
>>> signals" in PyQt [...]
>> Yes, this is in fact documented. I guess these short-circuit signals are
>> similar to the good old PYSIGNALs in PyQt3.
>>
>> But this still does not answer my question: what does "PyObject" means in
>> the signature of a signal?
> 
> I'd just assumed any valid identifier.

I'm asking because I got segfaults when trying to pass python objects around 
using SIGNALs and "PyObject" in the signature. Specifically, it seems that the 
objects go through a SIP wrap/unwrap cycle, because the slot function receives 
an object with a different id().

I was thinking that PyObject meant something like "any object wrapped by SIP", 
but I can't understand the exact meaning.
-- 
Giovanni Bajo

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]