mgear.vendor.Qt module

Minimal Python 2 & 3 shim around all Qt bindings

DOCUMENTATION was born in the film and visual effects industry to address the growing need for the development of software capable of running with more than one flavour of the Qt bindings for Python - PySide, PySide2, PyQt4 and PyQt5.

  1. Build for one, run with all

  2. Explicit is better than implicit

  3. Support co-existence

Default resolution order:
  • PySide2

  • PyQt5

  • PySide

  • PyQt4


>> import sys >> from Qt import QtWidgets >> app = QtWidgets.QApplication(sys.argv) >> button = QtWidgets.QPushButton(“Hello World”) >> >> app.exec_()

All members of PySide2 are mapped from other bindings, should they exist. If no equivalent member exist, it is excluded from and inaccessible. The idea is to highlight members that exist across all supported binding, and guarantee that code that runs on one binding runs on all others.

For more details, visit


See end of file for license (MIT, BSD) information.