Difference between revisions of "Qt for Python/GettingStarted"

From Qt Wiki
Jump to: navigation, search
(Considerations before starting)
m (Started PySide2)
Line 1: Line 1:
 
== Considerations before starting ==
 
== Considerations before starting ==
  
PySide2 supports Python 2 (recommended: 2.7 onwards) and Python 3 (recommended: 3.5 onwards).  
+
PySide2 supports Python 2 (recommended: 2.7 onwards, Compatibility module ''six'' installed) and Python 3 (recommended: 3.5 onwards).  
  
When planning development, it is helpful to have debug binaries and/or symbols for Python available. On Windows, this is done choosing ''Customized Installation'' when installing python and ticking the respective check boxes. On Linux, debug packages can be installed in addition.
+
Currently, only Qt 5.6 is supported. Qt needs to be build with the ''QtXmlPatterns'' module.
  
For development, 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.
+
=== Development ===
 +
 
 +
Development happens in the dev branches of the [http://code.qt.io/cgit/pyside/pyside-setup.git/ repositories]. Contributions follow the [[Qt_Project_Guidelines|standard process]].
 +
 
 +
It is helpful to have debug binaries and/or symbols for Python available. On Windows, this is done choosing ''Customized Installation'' when installing python and ticking the respective check boxes. On Linux, debug packages can be installed in addition. For Ubuntu, the packages python3-dbg, libpython3-dbg provide a debug binary python3-dbg.
 +
 
 +
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 Linux, the command
 +
virtualenv -p /usr/bin/python3-dbg testenv
 +
creates a Virtual Environment named ''testenv'' for debugging purposes. On Windows, an installation step may be required:
 +
python -m pip install virtualenv
 +
python -m virtualenv testenv
 +
 
 +
The Virtual Environment is activated by
 +
  source testenv/bin/activate
 +
or
 +
CALL testenv\Scripts\activate.bat

Revision as of 12:15, 29 August 2016

Considerations before starting

PySide2 supports Python 2 (recommended: 2.7 onwards, Compatibility module six installed) and Python 3 (recommended: 3.5 onwards).

Currently, only Qt 5.6 is supported. Qt needs to be build with the QtXmlPatterns module.

Development

Development happens in the dev branches of the repositories. Contributions follow the standard process.

It is helpful to have debug binaries and/or symbols for Python available. On Windows, this is done choosing Customized Installation when installing python and ticking the respective check boxes. On Linux, debug packages can be installed in addition. For Ubuntu, the packages python3-dbg, libpython3-dbg provide a debug binary python3-dbg.

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 Linux, the command

virtualenv -p /usr/bin/python3-dbg testenv

creates a Virtual Environment named testenv for debugging purposes. On Windows, an installation step may be required:

python -m pip install virtualenv
python -m virtualenv testenv

The Virtual Environment is activated by

 source testenv/bin/activate

or

CALL testenv\Scripts\activate.bat