I have been working with PyQt on a daily bases for the last four years
and had a look at PySide too (its 99% the same). When it comes to
stability and ease of compillation PyQt is the winner for me (had a few
problems with programs shutting down with a segfault where PyQt was
good). Now since it comes with Nuke and Maya (and Houdini later on, RFE
is in) this is the way to go for projects concerning those packages.
Riverbank Computing has done very little with PyQt and now that
PySide is coming with Maya 2014, definitely go with PySide.
This is not true. I think we won't see Qt5 support in PySide very soon
(whereas PyQt will get it quite soon and already has it for some parts
of Qt). There is also a nice abstraction layer called "dip", which helps
you build enterprise grade apps in no time. Right now I would also
choose PyQt over PySide because there has been some serious talk on the
mailing list to basically rewrite everyting (the binding generators
shiboken) and also the current maintainer stepped down in March due to
the funding stopped by Nokia. It was also discussed as being "dead" on
the current mailing list. Times are a little uncertain for PySide with
Digia the new Qt owner not taking this over. There is a new maintainer
now (John from wingware) but I don't know how much contributions there
will be from the community since shiboken seems quite involved....
Having said all this, for some code I have already done the move from
PyQt to PySide and back again and it did not take me long to do the
transition each time. Make sure you use sip.api v2 in PyQt. The slots
might need some redoing, too. But thats easy as well.
Cheers
Sebastian
On 5 April 2013 14:51, Elias Ericsson Rydberg
<elias.ericsson.rydb...@gmail.com
<mailto:elias.ericsson.rydb...@gmail.com>> wrote:
If I'm not mistaken PyQt requires some kind of license if you want
to ship your application while PySide doesn't. I've been
recommended PySide over PyQt, and since both Maya and Nuke
supports it I would go with PySide.
2013/4/5 Fredrik Averpil <fredrik.aver...@gmail.com
<mailto:fredrik.aver...@gmail.com>>
Nuke comes with PySide and Maya 2014 is coming out with PySide
support too.
I'm in the process of building a cross-platform standalone
(and in-house) Python app with either PyQt and PySide, as
parts of it also needs to run inside (integrated into) Maya
and Nuke respectively. Would it be wise to entirely go for
PySide now that both Maya and Nuke will have this from start
(thus utilizing PySide for all variations of this app)?
I've heard that the development of PySide has somewhat
stagnated. I have no idea if that's the case though. What
would you think?
// Fredrik
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk
<mailto:Nuke-python@support.thefoundry.co.uk>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk
<mailto:Nuke-python@support.thefoundry.co.uk>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
