[Documentation] [TitleIndex] [WordIndex

  Show EOL distros: 

python_qt_binding

Package Summary

This stack provides Python bindings for Qt. There are two providers: pyqt and pyside. PyQt is released under the GPL, which can be too restrictive. Therefore this package also provides PySide when available. PySide uses the LGPL license, but is not available via normal Debian package channels on Ubuntu Lucid. Both the bindings and tools to build bindings are included from each available provider. For PyQt, this is called "SIP". For PySide, it is called "Shiboken" (and other tools). Also provided is adapter code to make the user's Python code independent of which binding provider was actually used.

Package Summary

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.

Package Summary

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.

Package Summary

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.

Package Summary

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.

Package Summary

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.

  • Maintainer status: maintained
  • Maintainer: Claire Wang <clairewang AT openrobotics DOT org>, Shane Loretz <sloretz AT openrobotics DOT org>
  • Author: Dave Hershberger, Dorian Scholz, Dirk Thomas
  • License: BSD
  • Source: git https://github.com/ros-visualization/python_qt_binding.git (branch: kinetic-devel)

Package Summary

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.

Package Summary

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.

  • Maintainer status: maintained
  • Maintainer: Claire Wang <clairewang AT openrobotics DOT org>, Shane Loretz <sloretz AT openrobotics DOT org>
  • Author: Dave Hershberger, Dorian Scholz, Dirk Thomas
  • License: BSD
  • Source: git https://github.com/ros-visualization/python_qt_binding.git (branch: melodic-devel)

Package Summary

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.

  • Maintainer status: maintained
  • Maintainer: Claire Wang <clairewang AT openrobotics DOT org>, Shane Loretz <sloretz AT openrobotics DOT org>
  • Author: Dave Hershberger, Dorian Scholz, Dirk Thomas
  • License: BSD
  • Source: git https://github.com/ros-visualization/python_qt_binding.git (branch: melodic-devel)

Tutorials

Design

This python_qt_binding pkg is planned to become standalone (= separated from ROS). See discussion. It is already available via PyPI.


2024-10-05 14:27