Hello,
We are porting (at last) our codebase on python 3 but need retrocomp with python 2, thus we are using "future".
I have some questions about future behavior and the Qt Objects. I am surprised that declaring some QtCore.Signal(object) after "from builtins import object" line in a file, do not raise any issue in python 2. From my understanding, it really declares QtSignal(newObject), the one from the future module, isn't it ? I am pushing, to this signal attribute, a class that inherits from QtCore.QObject (So I guess not inheriting from newObject) and it still works like a charm. Does anybody have an explanation about that ?
The thingh is : this code works in *almost* every soft we use our scripts with (Autodesk Maya, SideFX Houdini, Unreal) but fails on Foundry Katana, pointing the above mismatch (newobject / object), and I am trying to understand what can explain the difference. Could a bad future module install on Katana explain that ?
Thanks in advance for any advice !
Best regards,
Sebastien
We are porting (at last) our codebase on python 3 but need retrocomp with python 2, thus we are using "future".
I have some questions about future behavior and the Qt Objects. I am surprised that declaring some QtCore.Signal(object) after "from builtins import object" line in a file, do not raise any issue in python 2. From my understanding, it really declares QtSignal(newObject), the one from the future module, isn't it ? I am pushing, to this signal attribute, a class that inherits from QtCore.QObject (So I guess not inheriting from newObject) and it still works like a charm. Does anybody have an explanation about that ?
The thingh is : this code works in *almost* every soft we use our scripts with (Autodesk Maya, SideFX Houdini, Unreal) but fails on Foundry Katana, pointing the above mismatch (newobject / object), and I am trying to understand what can explain the difference. Could a bad future module install on Katana explain that ?
Thanks in advance for any advice !
Best regards,
Sebastien