I am trying to port a big PyQt4 application to PySide, and I have face
many stacktraces, but now I've got a condition when PySide crashes
Python. Is this ok in PySide world? Shouldn't this condition be
intercepted and displayed as Python stacktrace? How can I quickly
debug why this happens?
Problem signature:
Problem Event Name: APPCRASH
Application Name: python.exe
Application Version: 0.0.0.0
Application Timestamp: 4c73f7b6
Fault Module Name: pyside.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4c8a4a67
Exception Code: c0000005
Exception Offset: 000075fc
OS Version: 6.0.6002.2.2.0.768.2
Locale ID: 1033
Additional Information 1: 6b10
Additional Information 2: f4cb88429c2d2426938798bc8ad92e70
Additional Information 3: b088
Additional Information 4: 1bc51873acf931b0d4f41c4bc4fa2232
--
anatoly t.
_______________________________________________
PySide mailing list
PyS...@lists.openbossa.org
http://lists.openbossa.org/listinfo/pyside
from PySide.QtGui import QWidget, QApplication, QMainWindow
class ExternalConsole(QWidget):
def __init__(self, parent):
self.light_mode = False
QWidget.__init__(self, parent)
class MainWindow(QMainWindow):
def __init__(self):
super(MainWindow, self).__init__()
self.extconsole = ExternalConsole(self)
app = QApplication([])
main = MainWindow()
print "impossible"
main.show()
app.exec_()
--
anatoly t.
You can make this work in current release just changing the order of
you call the base constructor.
class ExternalConsole(QWidget):
def __init__(self, parent):
QWidget.__init__(self, parent)
self.light_mode = False # << put this after base constructor call
BR
--
Renato Araujo Oliveira Filho
Instituto Nokia de Tecnologia - INdT
Mobile: +55 (81) 8704-2144
Thanks. Are there any plans to release 0.4.2 version?
--
anatoly t.
(sorry about the delay.)
We have had initial discussion about doing the next release in the
beginning of our next sprint. In practice, the source packages would be
available approximately two weeks from now.
Cheers,
ma.