Bug 319 – Unable to define a signal with tuple payload

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 319 - Unable to define a signal with tuple payload

Summary:

Unable to define a signal with tuple payload

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	HEAD
Platform:	All All

Importance:	P5 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-26 10:37 EEST by Matti Airas
Modified:	2010-09-10 19:21 EEST (History)
CC List:	9 users (show)

See Also:

Attachments
Sample code (499 bytes, text/x-python) 2010-08-26 10:37 EEST, Matti Airas	Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Matti Airas 2010-08-26 10:37:49 EEST

Created attachment 67 [details]
Sample code

If I define a signal with tuple argument, I get:

Traceback (most recent call last):
  File "./tupletest.py", line 21, in <module>
    someone.speak.emit(("one","two","three"))
TypeError: Unknown type used to emit a signal: tuple


Sample attached. The sample works if tuple is changed to object.

Comment 1 renato filho 2010-08-26 16:23:46 EEST

Fixed on commit:

Shiboken:

commit 47ab0d6bb7203c9a33c53d1b6d93f6305413c8e4
Author: Renato Filho <renato.filho@openbossa.org>
Date:   Thu Aug 26 11:47:55 2010 -0300

PySide:

commit a2f3e249bc0543b522c7d0e516dd07326e3ea7de
Author: Renato Filho <renato.filho@openbossa.org>
Date:   Thu Aug 26 15:23:23 2010 -0300