Currently I revisited some GUI programming for some weekends project with some friends at https://github.com/jendralhxr/uget2/. Our go-to python guy used to like guizero, but recently he is trying out tkinter and customTkinter. I have never really tried Tk and later found that customTkinter model-view-controller model is not as fluid as I experienced with Qt.
Hence, I revisited the community-official Qt-Python affairs: (saner person would just call these bindings instead)
- https://pypi.org/project/PySide/ (for Qt 4.8, it's okay since it was the first attempt)
- https://pypi.org/project/PySide2/ (for Qt 5.x, but why 2 as for 5?)
- https://pypi.org/project/PySide6/ (for Qt 6.x)
Thankfully, the official-official version has better naming scheme that is self-explanatony:
But this version was said to be lagged for a while during Qt 5 term, albeit started earlier during the Qt 4 days. Company stuff, I guess.
All the projects are good with wonderful people working behind/on them. But this is what I don't really like with python people: how to pass on legacies (not quite respecting legacy code base, compatibility issues with third-party libraries, reluctance to re-study/re-write the code, and the inertial needs to keep the business going with developmental code).
I guess as end user, we can use them wisely and adapt to changes, swiftly.