4 ms·
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
by rtpg 8y ago
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.
- antnisp 8y agoIsn't the licensing LGPL3? How is this confusing?
- mattip 8y agoHow 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?
- pjmlp 8y agoQt license is pretty ok, it is just complicated for the typical crowd that wants to sell stuff built with free (beer) tools.
- rtpg 8y agoI 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.