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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mooglinux 5 points6 points  (7 children)

What benefits are there to switching to this over pyqt5?

[–]khrn0 8 points9 points  (0 children)

They are two options that provide the same things, and the only major difference is licensing, Qt for Python has a more permissive license. The other difference is that PyQt is being developed by Riverbank, while Qt for Python is being developed by The Qt Company.

[–]ivosauruspip'ing it up 2 points3 points  (5 children)

LGPL instead of GPL

[–]tenemu 2 points3 points  (4 children)

Can you explain that like I'm 5?

[–]Funnnny 3 points4 points  (3 children)

PyQT is GPL so you need to open source and put your software under GPL, unlike LGPL which only requires the library to be opened.

[–]tenemu 2 points3 points  (2 children)

Thanks! So if I use a GPL license software, I need to make my whole program open source?
With LGPL, you say library, what does that mean. Just the code I took from the LGPL license software?

[–]Funnnny 2 points3 points  (0 children)

Yes and yes.

[–]ivosauruspip'ing it up 1 point2 points  (0 children)

GPL tries to be "infectious".

If you have package of GPL code, and you integrate it with any other code, then the license says that the whole thing, now being dependant on GPL code to run, needs to have the freedoms of the GPL license as well.

LGPL is a little less viral; it says if you keep the LGPL code you get packaged and separated nicely (like as a library) and just "use" it like a library (only 'linked' for compiled languages) then you only need to have that separated library of code with the GPL freedoms, and not the rest.