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

List:       pykde
Subject:    Re: [PyQt] TypeError: type 'str' is not supported as a pyqtSignal()
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2010-07-31 8:23:42
Message-ID: 41436ad6cba12e49ca1a9b9fcabf5a53 () localhost
[Download RAW message or body]

On Fri, 30 Jul 2010 15:29:33 -0700 (PDT), Demetrius Cassidy
<dcassidy36@mass.rr.com> wrote:
> I believe the single quotes would return a python str object. Now that I
> think about it you are correct that string itself is not a type. But you
> should be able pass a string instead of another object to get the same
> results. At least that always worked for me prior to this release.
> 
> These fail:
>>>> pyqtSignal('str')
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> TypeError: type 'str' is not supported as a pyqtSignal() type argument
type
>>>> pyqtSignal('list')
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> TypeError: type 'str' is not supported as a pyqtSignal() type argument
type
> 
> But these work:
>>>> pyqtSignal(str)
> <unbound signal >
>>>> pyqtSignal(list)
> <unbound signal >
>>>>
> 
> I am not sure if the above was working due to a bug that was fixed, or
if
> this change was intentional?

Either way, the current behaviour is correct.

Phil
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]