Bug 790 – QStyledItemDelegate Signal with lambda and QModelIndex: Fatal Python error: PyEval_SaveThread: NULL tstate

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 790 - QStyledItemDelegate Signal with lambda and QModelIndex: Fatal Python error: PyEval_SaveThread: NULL tstate

Summary:

QStyledItemDelegate Signal with lambda and QModelIndex: Fatal Python error: P...

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	QtGui
Version:	1.0.0
Platform:	All All

Importance:	P2 normal
Assigned To:	Hugo Parente Lima

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-03-24 22:38 EET by Max A. Busse
Modified:	2011-04-01 23:16 EEST (History)
CC List:	9 users (show)

See Also:

Attachments
Example Implementation (1.35 KB, text/x-python) 2011-03-24 22:39 EET, Max A. Busse	Details
Example Implementation Output (98 bytes, application/octet-stream) 2011-03-24 22:39 EET, Max A. Busse	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 Max A. Busse 2011-03-24 22:38:37 EET

When a Widgets Event created in the Delegate Class in a ModelView, is connected
using lambda passing the QModelIndex to the function, the program crashes with
the message:

Fatal Python error: PyEval_SaveThread: NULL tstate


If the ModelIndex is not passed, this problem does not exist.


Also, this problem does not exist in PySide 0.4.2 but in 1.0.0, betas not
tested.

Comment 1 Max A. Busse 2011-03-24 22:39:15 EET

Created attachment 288 [details]
Example Implementation

Comment 2 Max A. Busse 2011-03-24 22:39:39 EET

Created attachment 289 [details]
Example Implementation Output

Comment 3 Hugo Parente Lima 2011-03-25 00:10:24 EET

Thanks for the report, it will probably be fixed before the next release next
week.

Comment 4 Hugo Parente Lima 2011-03-25 22:35:29 EET

An one line fix :-)

Fixed in commit:
pyside/9024884495b9a19368b64c96eb75ddb117b1e5c3

Comment 5 Hugo Parente Lima 2011-04-01 23:16:07 EEST

Closing bug after release of PySide 1.0.1.