Qt for Python/GettingStarted/MacOS
- Xcode 8.2 (macOS 10.11), 8.3.3 (macOS 10.12), 9 (macOS 10.13), 10.1 (macOS 10.14)
- A Python interpreter (version Python 3.6 or Python 2.7). One possibility is to to use a package from https://www.python.org/downloads/ , it is also possible to use a Homebrew / MacPorts provided python.
- System Python usage is discouraged, because package installation will attempt to write into system folders and might fail in different ways because of system permissions (unless you use a virtualenv)
- Qt 5.12
- libclang 6.0+ (for 5.12)
- CMake from https://cmake.org/download/ (>= 3.1)
- Git (>=2)
- virtualenv (strongly recommended, but optional)
- Python sphinx package for documentation (optional, pip install sphinx) - documentation generation currently does not work on maCOS
- No OpenSSL is required because Qt uses Secure Transport (Apple) instead.
Building from sources
[Optional but recommended]: Creating a virtual environment using virtualenv
virtualenv allows you to create a local, user-writeable copy of a python environment into which arbitrary modules can be installed and which can be removed after use.
- virtual testenv
- . testenv/bin/activate
will create and use a new virtual environment, which is indicated by the command prompt changing.
Setting up CLANG
- Download libclang, e.g.
- Extract the files, e.g.
7z x libclang-release_60-mac-clazy.7z
- Export the installation path to the path you choosed to place the files
- Clone the official repository
git clone --recursive https://code.qt.io/pyside/pyside-setup
- Check out the version you want to build, e.g. 5.12 (Keep in mind you need to use the same version as your Qt installation)
cd pyside-setup && git checkout 5.12
- Check your Qt installation path, to specifically use that version of qmake to build PySide2:
- Strongly consider using a virtualenv (to avoid permission issues when building and installing)
virtualenv testenv; source testenv/bin/activate
- Check which Python interpreter is being picked up in PATH (system one, homebrew one, MacPorts one, virtualenv one, or some other) because this influences where the PySide2 package will be installed:
- Build can take a few minutes, so it is recommended to use more than one CPU core (e.g. 8). Remember to replace the paths to your current qmake path:
python setup.py build --qmake=/path/to/qmake --build-tests --ignore-git --parallel=8
- To install the PySide2 package into the currently active Python environment (regular, or virtualenv), just run:
python setup.py install --qmake=/path/to/qmake --build-tests --ignore-git --parallel=8
- You can execute one of the examples to verify the process is properly working.
- Remember to properly set the environment variables for Qt and PySide2.
Development happens in the 5.12 and dev branches of the pyside-setup repository. The top level repository has the following submodules:
- sources/pyside2-tools: uic, rcc tools
- examples/ (5.6 only, examples are no longer a submodule in 5.9+)
Contributions follow the standard process. It is helpful to have debug binaries and/or symbols for Python available. On macOS you will need to build the Python interpreter with debug symbols by hand. It is also recommended to use a Virtual Environment for testing to be able to always start from a clean base and avoid issues with write permissions in installations. On macOS, the command
virtualenv -p /usr/bin/python3-dbg testenv
creates a Virtual Environment named testenv for debugging purposes. Before building the first time, the module Sphinx should be installed into the virtual environment:
pip install sphinx