Qt for Python/GettingStarted/MacOS: Difference between revisions
m (CristianMaureiraFredes moved page PySide2 MacOS macOS to PySide2 MacOS) |
No edit summary |
||
(28 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
[[Category:Qt for Python]] | |||
==== | == Official documentation == | ||
Refer to the [https://doc.qt.io/qtforpython/gettingstarted-macOS.html official docs] to get started on macOS. | |||
== Development == | |||
Development happens in the 5.15 and dev branches of the [http://code.qt.io/cgit/pyside/pyside-setup.git/ pyside-setup repository]. | |||
== Development == | |||
Development happens in the 5. | |||
The top level repository has the following submodules: | The top level repository has the following submodules: | ||
* sources/pyside2-tools: | * sources/pyside2-tools: pyside2-lupdate | ||
Contributions follow the [[Qt_Project_Guidelines|standard process]]. | Contributions follow the [[Qt_Project_Guidelines|standard process]]. | ||
It is helpful to have debug binaries and/or symbols for Python available. | 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. | On macOS you will need to build the Python interpreter with debug symbols by hand. | ||
It is also recommended to use a [http://docs.python-guide.org/en/latest/dev/virtualenvs/ Virtual Environment] for testing to be able to always start from a clean base and avoid issues with write permissions in installations. | |||
It is also recommended to use a [http://docs.python-guide.org/en/latest/dev/virtualenvs/ 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 | On macOS, the command | ||
virtualenv -p /usr/bin/python3-dbg testenv | virtualenv -p /usr/bin/python3-dbg testenv | ||
creates a Virtual Environment named ''testenv'' for debugging purposes. | creates a Virtual Environment named ''testenv'' for debugging purposes. | ||
Before building the first time, the module [http://www.sphinx-doc.org/en/1.4.9/ Sphinx] should be installed into the virtual environment: | Before building the first time, the module [http://www.sphinx-doc.org/en/1.4.9/ Sphinx] should be installed into the virtual environment: | ||
pip install sphinx | pip install sphinx |
Latest revision as of 10:57, 2 January 2020
Official documentation
Refer to the official docs to get started on macOS.
Development
Development happens in the 5.15 and dev branches of the pyside-setup repository. The top level repository has the following submodules:
- sources/pyside2-tools: pyside2-lupdate
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