Originally posted by cipri
View Post
-
I just want to point out here that you're complaining that the platform they declared finished near the end of the 4.x series has issues with a platform it was never really designed to support. You're strongly suggested to use QML/Qt Quick Controls 2 for new developments instead, especially on Android. -
AFAIK Nokia wanted to buy PyQt to get complete control and both couldn't come to an understanding which is probably code for "Riverbank wanted more money" or so.Originally posted by habilain View PostLeave a comment:
-
No; PyQT is a project by Riverbank Computing, whereas Qt for Python is the new name for the old PySide project now that it's been officially endorsed by the QT company. The reason that there's two projects is that the older PyQT project is only GPLv3/Commercial, whereas the newer PySide/Qt for Python bindings are GPLv3/LGPLv3/Commercial i.e. the licensing is a bit easier.Originally posted by FireBurn View PostLeave a comment:
-
I would not advice anybody to use QT. It is very buggy, and the devs are more interested in bringing new features with even more bugs.
I give you one example of serious bug, that I was reporting nearly 5 years ago. The bug was confirmed, and tagged as "P2 Important".
It is still open today.
https://bugreports.qt.io/browse/QTBUG-43635
And then I contacted someone that is responsible for the QT development on Android , and he said, he can solve it, but it costs, if I remember correctly 7.000 or 7.500 euro, and that is the minimal fee that ask for solving a bug.
Does QT still belong to Trolltech? because that name really fits them.
This is such a buggy framework, and then on top it has this restrictive License.
Leave a comment:
-
Qt 6 Will Bring Improvements To The Toolkit's Python Support
Phoronix: Qt 6 Will Bring Improvements To The Toolkit's Python Support
Adding to the interesting objectives for Qt 6 are further enhancements to "Qt for Python" for enhancing the programming language's support for this tool-kit...
Leave a comment: