PyQt
-
I notice that PySide is specifically called out in this subforum. Is pyside the only blessed python binding discussed here, or are PyQt discussions also welcome?
Personally I only use PyQt because it's what I started playing with years ago.
-
PyQt questions are fine and are best posted to this forum, I would suggest. Both bindings can be discussed here.
I started Qt with PyQt (now use C++). Then it was PySide2 vs PyQt5, and PySide2 just wasn't up to it, loads of "holes". The jump of 4 major releases to PySide6 sure helped, and now from what I can tell it is just about as good as PyQt6.
There are times with a very specific PyQt question that we have to refer to people to the riverbank mailing list for further information.
-
I notice that PySide is specifically called out in this subforum. Is pyside the only blessed python binding discussed here, or are PyQt discussions also welcome?
Personally I only use PyQt because it's what I started playing with years ago.
@Kent-Dorfman hi,
I concur with @JonB, questions around PyQt have been around for a long time and there is no problem with that.
I memory serves well, we renamed the category to Qt for Python to make it more generic when PySide6 was released as for a very long time only PyQt was available.
Small note, the jump from 2 to 6, has nothing to do with major versions, it was just to make it match the Qt version.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
@Kent-Dorfman hi,
I concur with @JonB, questions around PyQt have been around for a long time and there is no problem with that.
I memory serves well, we renamed the category to Qt for Python to make it more generic when PySide6 was released as for a very long time only PyQt was available.
Small note, the jump from 2 to 6, has nothing to do with major versions, it was just to make it match the Qt version.
Small note, the jump from 2 to 6, has nothing to do with major versions, it was just to make it match the Qt version.
I know :) It was just that it was a jump of 4! Still nowhere near keeping up with the current major versions of Creator, which is one of my bug bears....!
-
I know :) It was just that it was a jump of 4! Still nowhere near keeping up with the current major versions of Creator, which is one of my bug bears....!
I know I don't like that as well, but at least it reduced the confusion between Qt and QtCreator versions by an order of magnitude in posts here on the platform
Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct
Q: What's that?
A: It's blue light.
Q: What does it do?
A: It turns blue. -
I know :) It was just that it was a jump of 4! Still nowhere near keeping up with the current major versions of Creator, which is one of my bug bears....!
I know I don't like that as well, but at least it reduced the confusion between Qt and QtCreator versions by an order of magnitude in posts here on the platform
I know I don't like that as well, but at least it reduced the confusion between Qt and QtCreator versions by an order of magnitude in posts here on the platform
Not sure what you mean. I started at Qt5 a few years ago. We are now at Qt6. Meanwhile Creator went from something like major version 4 to major version 19, or thereabouts. I can't really see much has even changed in it (at least for my usage; and for me it has about the same number of major bugs/annoyances as it did at version 4, no improvements in lots of those). Certainly not enough to justify ~15 major version increments. If this were any other product than Qt, which I do love, I would not touch it with a bargepole if it need to undergo so many, frequent major version numbers.
