[PyQt] Fwd: pyqt4-dev-tools: defining a pyqtSignal(str) fires a pyqtSignal(QString).
Phil Thompson
phil at riverbankcomputing.com
Sun Jun 21 14:01:40 BST 2015
On 20/06/2015 1:52 pm, Dmitry Shachnev wrote:
> Hi Enno,
>
> Forwarding your bug report to upstream mailing list.
>
> --
> Dmitry Shachnev
>
> ---------- Forwarded message ----------
> From: Enno <enno.vet at gmx.net>
> Date: 2015-06-19 23:39 GMT+03:00
> Subject: Bug#789330: pyqt4-dev-tools: defining a pyqtSignal(str) fires
> a pyqtSignal(QString).
> To: Debian Bug Tracking System <submit at bugs.debian.org>
>
>
> Package: pyqt4-dev-tools
> Version: 4.11.3+dfsg-2
> Severity: normal
>
> Dear Maintainer,
>
> * What led up to the situation?
> Defined a class with signals:
> class Blahwoof(QMainWindow):
> helpsig = pyqtSignal(str)
> ...
>
> Connected the signal to a function:
> def react(self, sig='poof'):
> self.helpsig.emit(sig)
>
> Defined a function catching that signal, but instead of a <str> a
> <QString> was received.
>
> If I define the signal as:
> helpsig = pyqtSignal(object)
>
> the function receives a <str>.
>
> This happens since about 4.11.2+dfsg-1, before it worked fine with the
> pyqtSignal(str) definition.
I can't find a version where it behaved differently - I went back as far
as v4.10.1. I'm also inclined to call it a feature rather than a bug.
Phil
More information about the PyQt
mailing list