Qt.py

Qt.py enables you to write software that dynamically chooses the most desireable bindings based on what's available, including PySide2, PyQt5, PySide and PyQt4; in that (configurable) order (see below).

Guides

• Developing with Qt.py
• Dealing with Maya 2017 and PySide2

Table of contents

• Install
• Usage
• Documentation
• Rules
• How it works
• Known problems
• Who's using Qt.py?
• Projects using Qt.py
• Projects similar to Qt.py
• Developer guide

Project goals

Write for PySide2, run in any binding.

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

Goal	Description
Support co-existence	Qt.py should not affect other bindings running in same interpreter session.
Build for one, run with all	Code written with Qt.py should run on any binding.
Explicit is better than implicit	Differences between bindings should be visible to you.

See CONTRIBUTING.md for more details.

Install

Qt.py is a single file and can either be copy/pasted into your project, downloaded as-is, cloned as-is or installed via PyPI.

$ pip install Qt.py

• Pro tip: Supports vendoring

Usage

Use Qt.py as you would use PySide2.

import sys
from Qt import QtWidgets

app = QtWidgets.QApplication(sys.argv)
button = QtWidgets.QPushButton("Hello World")
button.show()
app.exec_()

• Also see /examples

Documentation

All members of Qt stem directly from those available via PySide2, along with these additional members, accessible via Qt.QtCompat.

Attribute	Returns	Description
__binding__	str	A string reference to binding currently in use
__qt_version__	str	Reference to version of Qt, such as Qt 5.6.1
__binding_version__	str	Reference to version of binding, such as PySide 1.2.6
__wrapper_version__	str	Version of this project
__added__	list(str)	All unique members of Qt.py
__remapped__	list(str)	Members copied from elsewhere, such as QtGui -> QtWidgets
__modified__	list(str)	Existing members modified in some way
__shim__	module	Reference to original Qt.py Python module
load_ui(fname=str)	QObject	Minimal wrapper of PyQt4.loadUi and PySide equivalent
translate(...)	function	Compatibility wrapper around QCoreApplication.translate
setSectionResizeMode()	method	Compatibility wrapper around QAbstractItemView.setSectionResizeMode

Example

>>> from Qt import QtCompat
>>> QtCompat.__binding__
'PyQt5'

Branch binding-specific code

Some bindings offer features not available in others, you can use __binding__ to capture those.

if "PySide" in QtCompat.__binding__:
  do_pyside_stuff()

Override preferred choice

If your system has multiple choices where one or more is preferred, you can override the preference and order in which they are tried with this environment variable.

$ set QT_PREFERRED_BINDING=PyQt5  # Windows
$ export QT_PREFERRED_BINDING=PyQt5  # Unix/OSX
$ python -c "from Qt import QtCompat;print(QtCompat.__binding__)"
PyQt5

Constrain available choices and order of discovery by supplying multiple values.

# Try PyQt first and then PySide, but nothing else.
$ export QT_PREFERRED_BINDING=PyQt:PySide

Using the OS path separator (os.pathsep) which is : on Unix systems and ; on Windows.

Compile Qt Designer files

WARNING - ALPHA FUNCTIONALITY
See #132 for details.

.ui files compiled via pyside2-uic inherently contain traces of PySide2 - e.g. the line from PySide2 import QtGui.

In order to use these with Qt.py, or any other binding, one must first erase such traces and replace them with cross-compatible code.

$ pyside2-uic my_ui.ui -o my_ui.py
$ python -m Qt --convert my_ui.py
# Creating "my_ui_backup.py"..
# Successfully converted "my_ui.py"

Now you may use the file as you normally would, with Qt.py

Load Qt Designer files

The uic.loadUi function of PyQt4 and PyQt5 as well as the QtUiTools.QUiLoader().load function of PySide/PySide2 are mapped to a convenience function load_ui.

import sys
from Qt import QtCompat

app = QtWidgets.QApplication(sys.argv)
ui = QtCompat.load_ui(fname="my.ui")
ui.show()
app.exec_()

Please note, load_ui has only one argument, whereas the PyQt and PySide equivalent has more. See here for details - in a nutshell, those arguments differ between PyQt and PySide in incompatible ways.

sip API v2

If you're using PyQt4, sip attempts to set its API to version 2 for the following:

• QString
• QVariant
• QDate
• QDateTime
• QTextStream
• QTime
• QUrl

Rules

The PyQt and PySide bindings are similar, but not identical. Where there is ambiguity, there must to be a clear direction on which path to take.

Governing API

The official Qt 5 documentation is always right. Where the documentation lacks answers, PySide2 is right.

For example.

# PyQt5 adheres to PySide2 signals and slots
PyQt5.Signal = PyQt5.pyqtSignal
PyQt5.Slot = PyQt5.pyqtSlot

# PySide2 adheres to the official documentation
PySide2.QtCore.QStringListModel = PySide2.QtGui.QStringListModel

Portability

Qt.py does not hide members from the original binding. This can be problematic if, for example, you accidentally use a member that only exists PyQt5 and later try running your software with a different binding.

from Qt import QtCore

# Incompatible with PySide
signal = QtCore.pyqtSignal()

But it enables use of Qt.py as a helper library, in conjunction with an existing binding, simplifying the transition of an existing project from a particular binding.

# This is ok
from Qt import QtCore
from PyQt4 import QtGui

Caveats

There are cases where Qt.py is not handling incompatibility issues. Please see CAVEATS.md for more information.

How it works

Once you import Qt.py, Qt.py replaces itself with the most desirable binding on your platform, or throws an ImportError if none are available.

>>> import Qt
>>> print(Qt)
<module 'PyQt5' from 'C:\Python27\lib\site-packages\PyQt5\__init__.pyc'>

Here's an example of how this works.

Qt.py

import sys
import PyQt5

# Replace myself PyQt5
sys.modules["Qt"] = PyQt5

Once imported, it is as though your application was importing whichever binding was chosen and Qt.py never existed.

Known Problems

Send us a pull-request with known problems here!

• Maya and incompatible bindings on PYTHONPATH

Who's using Qt.py?

Send us a pull-request with your studio here.

• Atomic Fiction
• Industrial Brothers
• Moonbot Studios
• Sony Pictures Imageworks
• Colorbleed
• Method Studios
• Framestore
• Weta Digital
• Disney Animation
• Industriromantik
• Psyop
• ftrack

Presented at Siggraph 2016, BOF!

Projects using Qt.py

Send us a pull-request with your project here.

• https://github.com/BigRoy/maya-capture-gui
• https://github.com/pyblish/pyblish-lite
• https://github.com/fredrikaverpil/pyvfx-boilerplate
• https://gitlab.com/4degrees/riffle
• https://github.com/chadmv/cmt

Projects similar to Qt.py

Comparison matrix.

Project	Audience	Reference binding	License	PEP8	Standalone	PyPI	Co-existence
Qt.py	Film	PySide2	MIT	X	X	X	X
jupyter	Scientific	N/A	N/A	X
QtPy	Scientific	N/A	MIT		X	X
pyqode.qt	Scientific	PyQt5	MIT	X		X
QtExt	Film	N/A	N/A		X

Also worth mentioning, pyqt4topyqt5; a good starting point for transitioning to Qt.py.

Send us a pull-request with your project here.

Developer Guide

Tests are performed on each aspect of the shim.

• Functional
• Caveats
• Examples
• Membership

Each of these are run under..

• Python 2.7
• Python 3.4

..once for each binding or under a specific binding only.

Each test is run within it's own isolated process, so as to allow an import to occur independently from other tests. Process isolation is handled via nosepipe.

Tests that are written at module level are run four times - once per binding - whereas tests written under a specific if-statement are run only for this particular binding.

if binding("PyQt4"):
	def test_something_related_to_pyqt4():
		pass

Running tests

Due to the nature of multiple bindings and multiple interpreter support, setting up a development environment in which to properly test your contraptions can be challenging. So here is a guide for how to do just that using Docker.

With Docker setup, here's what you do.

# Build image
cd Qt.py
docker build -t mottosso/qt.py27 -f Dockerfile-py2.7 .
docker build -t mottosso/qt.py35 -f Dockerfile-py3.5 .

# Run nosetests
docker run --rm -v $(pwd):/Qt.py mottosso/qt.py27
docker run --rm -v $(pwd):/Qt.py mottosso/qt.py35

# Doctest: test_caveats.test_1_qtgui_qabstractitemmodel_createindex ... ok
# Doctest: test_caveats.test_2_qtgui_qabstractitemmodel_createindex ... ok
# Doctest: test_caveats.test_3_qtcore_qitemselection ... ok
# ...
#
# ----------------------------------------------------------------------
# Ran 21 tests in 7.799s
# 
# OK

Now both you and Travis are operating on the same assumptions which means that when the tests pass on your machine, they pass on Travis. And everybody wins!

See CONTRIBUTING.md for more of the good stuff.