So you have to write for qt5 bindings in order to fallback to older bindings? How does this help to limit refactoring on old scripts? (i.e. using the new QtWidgets instead of patching QtGui).
I’m sorry if you thought Qt.py would help you *convert your old scripts* into working with Python bindings for Qt5. Like Marcus said, you’d still have to write your scripts as if writing PySide2 code. Then it will offer a degree of binding agnosticism as well as a backwards compatibility to Qt4 bindings. I’ve heard good things about this conversion script which might help you with the conversion from PyQt4 to PyQt5: https://github.com/rferrazz/pyqt4topyqt5 I’ll only speak for myself, but in our studio, we’re now using PySide, PySide2 and PyQt5. We’re also using a mix of Python 2 and Python 3. I also write a lot of scripts which are intended to run in all those Python environments. For us, Qt.py really is a lifesaver. Don’t get me wrong, I have done and worked with similar solutions on different studios and I fully appreciate what they bring to the table (especially for in-house software where portability is not a big issue), but the way the project is presented is a bit miss-leading imho (and the default a bit odd). I would really wish to understand which part you felt was misleading so I can fix that. Was it my email, the blog posts or the Github repository? How do you mean that the default is a bit odd? We thought it would be a good idea to move forward with Qt5 and not get stuck, but offer a way to make those “new” scripts to actually run where only Qt4 bindings were available. Regards, Fredrik -- 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/CAD%3DwhWPAxuqfvcxor0%2B0UbtnGc6doJXkj0sWDq4vKonEUPGdBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
