Your message dated Mon, 22 Jun 2015 13:10:49 +0300
with message-id <[email protected]>
and subject line Re: pyqt4-dev-tools: defining a pyqtSignal(str) fires a
pyqtSignal(QString).
has caused the Debian Bug report #789330,
regarding pyqt4-dev-tools: defining a pyqtSignal(str) fires a
pyqtSignal(QString).
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
789330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789330
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 suppose it's an upstream item.
Brgds, e.
-- System Information:
Debian Release: 7.1
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.65-mash-rt94
Locale: LANG=de_AT@euro, LC_CTYPE=de_AT@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages pyqt4-dev-tools depends on:
ii libc6 2.19-11
ii libgcc1 1:4.8.1-2
ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libstdc++6 4.9.1-15
ii python 2.7.5-5
ii python-qt4 4.11.3+dfsg-2
pyqt4-dev-tools recommends no packages.
pyqt4-dev-tools suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Enno,
On Fri, 19 Jun 2015 22:39:48 +0200, Enno wrote:
> * 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 suppose it's an upstream item.
According to upstream response [1], this is a actually a feature:
"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."
Anyway, if you upgrade to pyqt5 or to new sip API, there will be no difference
between str and QString.
[1]: http://www.riverbankcomputing.com/pipermail/pyqt/2015-June/036073.html
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
