Ragnar Brynjúlfsson

Thanks for the quick reply.

If I set the QT_PREFERRED_BINDING=PySide2 environment variable, importing Qt.py no longer crashes Houdini, it just complains that it can't find any Qt bindings.

That said, it's not a big problem. I was just trying to see if I can find a clever solution that would work across Houdini, Maya 2106/17 and Nuke. There is not that much overlap in our code between the programs, so maintaining one version for each of PySide and PySide2 where needed isn't really a problem.

When you try importing PySide into Houdini 16, Houdini simply crashes. Now, this isn't really a problem, as Houdini 16 uses PySide2, and importing that works just fine.

But, we wanted to try to use Qt.py, which is a wrapper that let's you write Python Qt code compatible with PyQt4, PyQt5, PySide and PySide2. ( https://github.com/mottosso/Qt.py [github.com] ), and it too crashes when you import it.

Even doing the following crashes Houdini:

try:
import PySide
except ImportError:
import PySide2

By comparison, if I try to import PySide into Maya 2017, which also usese PySide2, it just gives an error that the module does not exist.

It's not a huge problem, but it would be nice to be able to write PySide dialogs that are compatible with Maya 2016 (Qt4), Maya 2017 (Qt5) and Houdini 16.

(I tested this with Houdini 16.0.504.20 on Ubuntu 14.04)