Qt for Python/GettingStarted
- Python: Python 3.5+ and Python 2.7 (Please notice there is a known issue with Python 3.6.0, read more.)
- Qt: 5.12 is recommended, but there are Technical Preview wheels for 5.11
- libclang: The libclang library (C-bindings), recommended: version 6 for PySide2 5.12.
- Prebuilt versions of it can be downloaded from download.qt.io.
- CMake (version >= 3.1 required) : The build system required by for building PySide2.
Install wheel from PyPi
Official release wheels of Qt For Python can be installed regularly via pip:
pip install PySide2
Note: This process will automatically install shiboken2 (python module) as dependency, but the package shiboken2_generator will not since it's the standalone binary that can generate Python bindings from a Qt/C++ project. We highly recommend to build PySide2 from scratch if you want to generate your own Python bindings from a Qt/C++ project, because the linking information will not be present in the shiboken2_generator wheel
Install wheel from Qt servers
Official release wheels of Qt for Python can be installed via pip but from Qt servers:
pip install --index-url=https://download.qt.io/official_releases/QtForPython/ pyside2 --trusted-host download.qt.io
Pre-release (snapshot) wheels containing the latest code changes are available at http://download.qt.io/snapshots/ci/pyside/ For example you can install the latest 5.12 snapshot wheel using:
pip install --index-url=http://download.qt.io/snapshots/ci/pyside/5.12/latest/ pyside2 --trusted-host download.qt.io
Building PySide2 from scratch
The building processes are covered in the platform pages.
- Mobile platforms are currently not supported (iOS, Android)
- Embedded Linux platforms are currently not supported (Raspberry Pi, iMX.6)
After cloning the official repository you must follow the instructions for your specific system.
setup.py build script
The script setup.py in the top level repository is used to build and install the PySide2 package. It takes a mode argument (build or install) and several options (more options are documented in setup.py itself).· The main options are:
- --qmake=/path/to/qmake: Path to qmake of the Qt library to be used
- --cmake=/path/to/cmake: Path to cmake binary
- --build-tests: Builds tests along with some helper packages
- --ignore-git: Prevents setup.py from cloning and checking out the git submodules.
- --debug: Build in Debug mode (some restrictions apply to Windows, see Build considerations)
- --reuse-build: Rebuilds only modified files
- --openssl=C:\Dev\qtdev\OpenSSL-Win64\bin: Path to OpenSSL's bindir which contains dlls (Only required for Windows PySide2 packages)
- --j / parallel # : Number of # processes to use when building
- --standalone: Copies over the Qt libraries (and other library dependencies) into the PySide2 package to make it work on other machines (on Windows all builds are standalone, even without specifying the command line argument).
- --verbose: Prints all compiler invocations when building the package.
A typical invocation looks like:
python setup.py install --build-tests --j 4
A successful build can be tested by running an example:
You can search for working examples by typing
cd sources/examples git grep "PySide2 port"
To perform all the available tests, just execute:
python testrunner.py test > testlog.txt
Note that to successfully run the tests on Windows you need to point the PATH environment variable to the Qt libdir:
Run only one test(qpainter_test):
ctest -R qpainter_test --verbose
Building the Documentation
Before you build pyside2, ensure that the following requirements are met, to be able to build the documentation:
- Install libXML2 and libXSLT before building PySide2:
apt-get install libxml2-dev libxslt1-dev # Ubuntu pacman -S libxml2 libxslt # Arch
- Set QT_SRC_DIR with the path to qtbase, if you don't want to build documentation based on the Qt sources under <QT_PKG_ROOT>/<QT_VERSION>/Src/qtbase.
- Install graphviz and sphinx
pip install graphviz sphinx
The build first runs qdoc on the Qt sources in $QT_SRC_DIR to generate the webxml files, which are then parsed by shiboken to generate reStructuredText files. In the final step, sphinx is run on the rst files to generate HTMLs.
You could also use the docrsts make target to generate only the reStructuredText files.
Using Qt Creator as a project explorer
Qt Creator 4.0+ can be used to open the PySide and Shiboken CMakeLists.txt files as projects, and thus provide usual IDE features for developing PySide - project file navigation, code completion (C++ only), following symbols under cursor (C++ only), syntax highlighting, locator usage, debugging, etc.
Currently there is a limitation that Shiboken has to be built first using the terminal, because the installed shiboken CMake packages will have to be specified for the PySide project in Qt Creator.
The steps for opening the projects in Qt Creator are:
- Open pyside-setup/sources/shiboken2/CMakeLists.txt, and specify a 5.12 Qt Kit to be used
- Build the project as usual (by pressing the build icon for instance)
- Open pyside-setup/sources/pyside2/CMakeLists.txt, and specify the same 5.12 Qt Kit
- Go to projects tab, and under the Build / CMake section find the Shiboken2_DIR setting. You have to specify the path to the folder where the Shiboken CMake package was installed when you compiled Shiboken from the terminal·
- An example path under MacOS is /Users/user/Dev/pyside2-setup/pyside_install/py3.6-qt5.12.1-64bit-debug/lib/cmake/Shiboken2-2.0.0. The path has to be adjusted depending on the user folder name, the version of python and qt, etc
- (Optional) On MacOS you also have to set the ALTERNATIVE_QT_INCLUDE_DIR setting to the Qt kit include path (e.g. /Users/user/Dev/qt511_source/include)
- Apply the CMake configuration changes (by pressing the button), and you should be able to build PySide
Now you can use the project explorer to look through the source cpp files, python files, use the locator feature to open files and file classes / methods, and other features that Qt Creator provides.
Troubleshooting / Known Issues
- Qt 5.9 does not work with OpenSSL 1.1
- When doing a custom Qt build (some unspecified versions for now), It is necessary to have an OpenSSL version of 1.0.x, since there are compatibility issues with newer versions of OpenSSL (see details)
- PySide2 looks at the system installation if the local Qt version does not have a required module
- The only workaround is to uninstall any module from the system, then PySide2 can look at only the Qt path currently being use.
- Qt packages that directly link to OpenSSL (as opposed to runtime discovery) are not currently supported.
- Make sure that the Python environment location where the PySide2 package will be installed is writable (otherwise you might get various permission denied errors). The install location can be found with 99% probability by running:
python -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())"