I’m in the process of rebuilding our python 2.7 libs for deadline, and noticed that the shipping SIP version is not compatible with our current standard version.
Do you guys plan on sticking with this current version of sip?
import sip
sip.SIP_VERSION_STR
‘4.15.4’
“the sip module implements API v10.0 to v10.1”
If yes, i would be more confident (need to rebuild pyqt whenever sip changes and wrangle some python config management).
(the version we use is 4.14.2, which uses API v8.1)
somewhat related, did you guys ever consider going the pyside route?
We currently have no plans to change the sip version for Deadline 7. The only reason it could happen before 7.0 is officially released is if we need to change the Qt/PyQt libraries due to some critical bug, but as far as we know the current versions of these libraries are solid. We also won’t consider changing versions of Qt/PyQt until the next major Deadline release (v8), so you won’t have to worry about re-compiling for 7.1, 7.2, etc.
As for PySide vs PyQt, I don’t actually recall. I think it had something to do with licensing…
PyQt uses GPL (or a commercial license, which im guessing you guys have, since i don’t see deadline opensourced 
), PySide uses LGPL, so without commercial license you can also bundle with commercial software, without having to opensource your main application.
In reality this usually means that programs supporting pyside can ship all dlls/code in a self contained form, and we don’t have to worry much about rebuilding anything.
Hm… seems like SIP changed versions in one of the 7 builds… on my building machine, it was using v4.15.4, but on other machines its using 4.16.2, which are incompatible.
Darn.
Yeah, it would have changed when we upgraded to Qt 5.3.1 for beta 3. But going forward, it shouldn’t change (unless of course we have to change Qt versions due to a bug, but the odds of that are pretty low).