PySide2: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Small Pyside 2 backlog added)
Line 13: Line 13:


<TODO>
<TODO>
=== 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 done. 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.
# Setup Bugreports & intropage for Pyside on wikis.qt.io (Alex)
# First time with Pyside (Document how to get started on this wiki)
# Code CLA (author agreements required)
# Testing Infrastructure
## What has been done so far?
## Qt CI
### make test
### cmake based build system (all repos)
### pip installable Pyside
#### CI has to setup virtual Python environment
#### Use pip to install/build Pyside
# Future changes to PySide
## Gaps (modules & API)
### No OpenGL support
### Plugin system (in what form or shape do we need it is uncertain - some failing tests exist already)
### Prepare a summary of gaps for other modules
## Fundamental Architecture changes
### Shiboken
#### Clang support
#### John Ehresmann wrote a python parser as Shiboken replacement
### QtQML?
## MyPy (type annotation - fully typed Python API)
## General Python features and their adoption in PySide (e.g. Async I/O)
## Creator and tooling

Revision as of 14:03, 14 April 2016

Pyside for Qt 5.x

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.

Tools

The following tools are used to develop PySide:

Getting started

<TODO>

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 done. 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. Setup Bugreports & intropage for Pyside on wikis.qt.io (Alex)
  2. First time with Pyside (Document how to get started on this wiki)
  3. Code CLA (author agreements required)
  4. Testing Infrastructure
    1. What has been done so far?
    2. Qt CI
      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
  5. Future changes to PySide
    1. Gaps (modules & API)
      1. No OpenGL support
      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
        2. John Ehresmann wrote a python parser as Shiboken replacement
      2. QtQML?
    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