News for hackers. Stuff that matters.
Re:Hello Qt for Python by rtpg on Saturday May 05, 2018 @10:46PM (#17005011)
wxPython is a thing that exists, and I believe it has a similar mental model to wxWidgets.

To be honest most of the QT solutions for Python are pretty fidgety . The recent wxPython releases (4.x) work out of the box direct from PyPI, not too much to worry about licensing.

For Qt, it's... the licensing is usually just fine for people but it's complex enough to where things like maintaining your own fork (pretty easy in Python compared to C++) is not super easy. But there's decent Python support, so it's more "do you want to use Qt or wx". Both systems have good enough support.

Re:Hello Qt for Python by pjmlp on Sunday May 06, 2018 @04:40AM (#17005739)
Qt license is pretty ok, it is just complicated for the typical crowd that wants to sell stuff built with free (beer) tools.
Re:Hello Qt for Python by rtpg on Sunday May 06, 2018 @07:00AM (#17006001)
I guess the proper rephrasing is that it doesn't match the licensing terms of most projects in the Python world.

It's most definitely not the most complicated thing, but when your processes are based off of BSD'd libraries, you gotta think a bit harder about Qt usage, if only for it falling outside the normal scope of things.

Re:Hello Qt for Python by antnisp on Sunday May 06, 2018 @03:19AM (#17005567)
Isn't the licensing LGPL3? How is this confusing?
Re:Hello Qt for Python by mattip on Sunday May 06, 2018 @07:51AM (#17006080)
How do I provide end users the ability to swap out LGPL3 shared objects (as required by the license) on an embedded platform with no access, or inside a py2exe bundle?