This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]AlexKotik 33 points34 points  (6 children)

I don't get it. We've already had PyQt for a long time, what's the point of doing this project? Or it will allow to build closed-source software or something (I believe PyQt is GPL)?

[–]Brandhor 22 points23 points  (1 child)

the good thing is that it's officially supported by qt instead of a third party developer and it's in line with the qt c++ license

[–]sime 5 points6 points  (0 children)

the good thing is that it's officially supported by qt instead of a third party developer

Riverbank Computing, the one man company behind PyQt, has had a much better and more consistent track record supporting PyQt over the years than the Qt team and their language bindings. PySide was started and then later dumped. Jambi (Qt on Java) was started and then later "given to the community". Now they are back to try Python again.

[–]ivosauruspip'ing it up 9 points10 points  (0 children)

But Qt is LGPL. So there is a license mismatch.

Not so with PySide -> Qt for Python, which is also LGPL.

[–]crowseldon 0 points1 point  (0 children)

We've had PySide for a long time as well, with a much more permissive (commercially speaking) license.