| python-pyqt |
4.12 |
Python Qt4 Bindings |
meta-qt4 |
| python-pyqt5 |
5.12.1 |
Python Qt5 Bindings |
meta-qt5 |
| python3-pyqt5 |
5.12.1 |
Python Qt5 Bindings |
meta-qt5 |
| python3-pyqt5 |
5.9.2 |
Python Qt5 Bindings |
meta-musicians |
| python-qt-bindingblacklisted |
0.4.0-1 |
This stack provides Python bindings for Qt. There are two providers: pyside and pyqt. PySide is released under the LGPL. PyQt is released under the GPL. Both the bindings and tools to build bindings are included from each available provider. For PySide, it is called "Shiboken". For PyQt, this is called "SIP". Also provided is adapter code to make the user's Python code independent of which binding provider was actually used which makes it very easy to switch between these. |
meta-ros1-melodic |
| python-qt-bindingblacklisted |
1.0.2-1 |
This stack provides Python bindings for Qt. There are two providers: pyside and pyqt. PySide2 is available under the GPL, LGPL and a commercial license. PyQt is released under the GPL. Both the bindings and tools to build bindings are included from each available provider. For PySide, it is called "Shiboken". For PyQt, this is called "SIP". Also provided is adapter code to make the user's Python code independent of which binding provider was actually used which makes it very easy to switch between these. |
meta-ros2-dashing |
| python-qt-bindingblacklisted |
1.0.3-1 |
This stack provides Python bindings for Qt. There are two providers: pyside and pyqt. PySide2 is available under the GPL, LGPL and a commercial license. PyQt is released under the GPL. Both the bindings and tools to build bindings are included from each available provider. For PySide, it is called "Shiboken". For PyQt, this is called "SIP". Also provided is adapter code to make the user's Python code independent of which binding provider was actually used which makes it very easy to switch between these. |
meta-ros2-eloquent |
| python-qt-bindingblacklisted |
1.0.5-1 |
This stack provides Python bindings for Qt. There are two providers: pyside and pyqt. PySide2 is available under the GPL, LGPL and a commercial license. PyQt is released under the GPL. Both the bindings and tools to build bindings are included from each available provider. For PySide, it is called "Shiboken". For PyQt, this is called "SIP". Also provided is adapter code to make the user's Python code independent of which binding provider was actually used which makes it very easy to switch between these. |
meta-ros2-foxy |
| qt-guiblacklisted |
0.4.0-1 |
qt_gui provides the infrastructure for an integrated graphical user interface based on Qt. It is extensible with Python- and C++-based plugins (implemented in separate packages) which can contribute arbitrary widgets. It requires either PyQt or PySide bindings. |
meta-ros1-melodic |
| qt-guiblacklisted |
1.0.7-1 |
qt_gui provides the infrastructure for an integrated graphical user interface based on Qt. It is extensible with Python- and C++-based plugins (implemented in separate packages) which can contribute arbitrary widgets. It requires either PyQt or PySide bindings. |
meta-ros2-dashing |
| qt-guiblacklisted |
1.0.7-1 |
qt_gui provides the infrastructure for an integrated graphical user interface based on Qt. It is extensible with Python- and C++-based plugins (implemented in separate packages) which can contribute arbitrary widgets. It requires either PyQt or PySide bindings. |
meta-ros2-eloquent |
| qt-guiblacklisted |
1.1.0-1 |
qt_gui provides the infrastructure for an integrated graphical user interface based on Qt. It is extensible with Python- and C++-based plugins (implemented in separate packages) which can contribute arbitrary widgets. It requires either PyQt or PySide bindings. |
meta-ros2-foxy |