Important: Please read the Qt Code of Conduct -

PySide - What are the community plans and future

  • PySide was introduced several years ago as a (more) official set of python bindings for Qt. After Qt bounced from Trolltech to Nokia to obscurity and back, PySide never seemed to recover. The last official release of PySide appears to have been v1.2.2 which supports Qt up to version 4.8. In July 2015, Qt released v5.5 of the C++ libraries. Needless to say, PySide is a ways behind.

    Also announced in the summer of 2015, were the draft plans for the 2016 VFX Reference Platform, recommending Qt 5.5 as the version of choice for some pretty major packages. First, a little background on what the VFX Reference Platform is. It's a group of technology leaders in the VFX community (including many major motion picture houses) pushing for standards on major VFX related packages, like packages from Autodesk (Maya, RV, Mudbox, etc), and The Foundry (Nuke, Katana, etc). However, one of the hurdles for moving to Qt 5.5 is the lack of PySide support.

    Python is a major piece of the technology pipeline for VFX houses, and many of the big supporters of Qt are these 3rd party VFX applications. In order to provide the ability to extend their applications, some have turned to PySide. PyQt has been used in the past but makes it much harder to freely distribute due to the more restrictive licensing (GPL vs LGPL).

    So far, I haven't found much information on the future of PySide, but it seems there is renewed interest in the project's success. It would be nice to hear from the PySide developers and other community members on what's happening with the project, and perhaps about how to jump start support for Qt 5+.

  • It appears that at least one person is trying to resurrect PySide in a new github repo.

Log in to reply