PySide2

En Ar Bg De El Es Fa Fi Fr Hi Hu It Ja Kn Ko Ms Nl Pl Pt Ru Sq Th Tr Uk Zh

Qt for Python

The Pyside 2 project aims to provide a complete port of PySide to Qt 5.x. The development started on GitHub in May 2015. The project managed to port Pyside to Qt 5.3, 5.4 & 5.5. During April 2016 The Qt Company decided to properly support the port (see details ).

This wiki page tracks the progress of PySide for Qt 5.x development and provides further information concerning the effort.

Getting Started

• Getting started guide for macOS, Windows and Linux
• Bug tracker to report any issue.
• CodeReview and PySide2 open patches
• Git repository (5.9 branch is the branch currently worked on for PySide2)
  • ssh://codereview.qt-project.org/pyside/pyside-setup
• Development: Getting started

Community

• Official IRC channel on FreeNode #qt-pyside
• Official Mailing list
• Keybase: keybase.io/team/pyside
• Gitter: gitter.im/PySide/pyside2

Development Status

Weekly development progress

The summary of the development progress can be found in Development Notes by date

Pyside Development Progress Notes

The most current view of the progress can be found in Jira:

1. Unresolved issues
2. All issues (including resolved)

The second link is useful to monitor the progress of the backlog. The best way to achieve this is to sort the list by the "Updated" column. Larger backlog/feature items are filed as "User Stories" in Jira.

Missing PySide2 bindings

The list of the current missing bindings can be found in:

• Missing PySide2 bindings

Outstanding tasks for release

1. Determine Pyside package number
2. Ensure multi target packages can be created (long standing - reduced Python API usage )
3. General Doc changes required for release
   1. Getting started
   2. Some examples documented
   3. pyinstaller usage
   4. Class documentation polish
   5. snapshot generation on http://doc-snapshot.qt-project.org/

Backlog

The list below represents some short term targets and long term ideas for Pyside2 development. There is no guarantee that this will happen as written down. It is meant as a short reminder and idea collection for future development. In the long term this list is likely to move to https://bugreports.qt.io/browse/PYSIDE.

1. First time with Pyside (Document how to get started on this wiki)
2. Testing Infrastructure
   1. What has been done so far?
   2. Qt CI support (PYSIDE-431)
      1. make test
      2. cmake based build system (all repos)
      3. pip installable Pyside
         1. CI has to setup virtual Python environment
         2. Use pip to install/build Pyside (release bundling)

1. Future changes to PySide
   1. Gaps (modules & API)
      1. Identify the extent of the gaps by porting existing examples from Qt4 to Qt5 (done)
      2. Plugin system (in what form or shape do we need it is uncertain - some failing tests exist already)
      3. Prepare a summary of gaps for other modules
   2. Fundamental Architecture changes
      1. Shiboken
         1. Clang support (PYSIDE-323)
      2. QtQML support (PYSIDE-355)
   3. MyPy (type annotation - fully typed Python API)
   4. General Python features and their adoption in PySide (e.g. Async I/O)
   5. Creator and tooling
      1. Fix QtC debugger to understand Python/C++ mixed internals
   6. Documentation generation
   7. Deployment of apps
   8. Debugging support

1. Must have tasks for first release
   1. Packaging (e.g. pip deployment? )
   2. Clarify Installer story
   3. Documentation
   4. Product placement decisions
      1. Licensing
      2. Naming
      3. etc
   5. Complete CI coverage