That's a shame. I like PySide a lot. I found it creates more readable code than PyQt. This move to PySide2 is certainly creating lots of headaches though, even after Marcus' excellent work in the Qt module.
On that subject, if you're using Maya 2017, get update 4. There are lots of fixes for PySide2 crashes in there. On Friday, 30 June 2017 07:36:27 UTC+10, dukecyto wrote: > > Thanks Justin and Marcus, > Makes me feel like staying away from using PySide... Seems like there > are too many surprise factors. > > 2017-06-29 6:08 GMT+00:00 Marcus Ottosson <[email protected] > <javascript:>>: > > I get this in PySide2 as well sometimes. > > > > from PySide2 import QtWidgets > > any_widget = QtWidgets.qApp.topLevelWidgets()[0] > > any_widget.parent() # Ok > > any_widget.parent() # Already deleted > > > > any_widget = QtWidgets.qApp.topLevelWidgets()[0] > > any_widget.parent().parent() # Ok > > any_widget.parent() # Already deleted > > > > We are experiencing crashes similar to what Ben reports, after we > started to > > make a shift to Qt.py just like Ben. > > > > If you happen to catch at which statement this happens, I can see if I > can > > protect against this in Qt.py, though odds are it runs deeper than that. > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/6c4228fc-099e-4ef7-b17a-a7ed24eb6f6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
