Thanks Marcus and Fredrik, I guess my confusion comes from reading this paragraphs, but *it's all clear now.* > This essentially makes all PySide/PyQt scripts written for Maya version <= 2016 unusable in Maya 2017. > To help fix this, and maintain backwards compatibility to previous versions of Maya, Marcus Ottosson and I created an open source project called Qt.py...
On the defaults I guess it depends on your goal/scope, what you describe makes perfect sense for distribution of new software that have to run within different environments (i.e. pyblish), but if you have an existing large codebase in your studio maybe it's more convenient to patch the new qtgui including the widgets at runtime (or account for this reality in some way). For the record, we have a similar python package extending and giving access to qt bindings at work and the migration wasn't a big deal, there's always some small percentage of 'TD code' around not following standards (therefore broken), but having control over the way tools/frameworks have access to the bindings is very important and I totally recommend it. Sorry for the trouble, Cheers! -- 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/CAPamJi8YiLmoegki8i%3DvDgk3GyCUx2xCLV9G4ys6dHSNetcZNg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
