On 12/14/2013 10:05 AM, Wolfgang Keller wrote: > PyQt looks native everywhere, but it might be a bit overweight, > depending on what you want to do and where your applications need to > run. > > And then there's the licensing issue, since PyQt, unlike Qt itself, is > not available under LGPL afaik. For closed-source commercial > applications, there seems to be a way to use a commercially licensed > PyQt (much less expensive than Qt itself) together with LGPL-Qt > however. Pyside would be a LGPL alternative to PyQt, but it doesn't > seem to be as up-to-date as PyQt.
I think PyQt is slowly being pushed aside in favor of PySide, which is more license-friendly for use in closed or open projects. I would recommend using PySide unless PyQt is a requirement for your project. -- https://mail.python.org/mailman/listinfo/python-list
