|
|
| (6 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| {{LangSwitch}}
| | #REDIRECT [[Qt_for_Python]] |
| [[Category:PySide]]
| |
| == Qt for Python ==
| |
| | |
| The Pyside 2 project aims to provide a complete port of [[PySide]] to Qt 5.x. The development started on [https://github.com/PySide 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 [https://groups.google.com/forum/#!topic/pyside-dev/pqwzngAGLWE details] ).
| |
| | |
| This wiki page tracks the progress of PySide for Qt 5.x development and provides further information concerning the effort.
| |
| | |
| == Getting Started ==
| |
| * [[PySide2_GettingStarted|Getting started guide for macOS, Windows and Linux]]
| |
| * [https://bugreports.qt.io/browse/PYSIDE Bug tracker] to report any issue.
| |
| * [https://codereview.qt-project.org CodeReview] and [https://codereview.qt-project.org/#/q/project:%255Epyside.%252B,n,z PySide2 open patches]
| |
| * Git repository (5.9 branch is the branch currently worked on for PySide2)
| |
| ** ssh://codereview.qt-project.org/pyside/pyside-setup
| |
| * [[PySide2_Development_Getting_Started|Development: Getting started]]
| |
| | |
| == Community ==
| |
| | |
| * Official IRC channel on FreeNode '''#qt-pyside'''
| |
| * [http://lists.qt-project.org/mailman/listinfo/pyside Official Mailing list]
| |
| * Keybase: [https://keybase.io/team/pyside keybase.io/team/pyside]
| |
| * Gitter: [http://gitter.im/PySide/pyside2 gitter.im/PySide/pyside2]
| |
| | |
| == Development Status ==
| |
| | |
| === Weekly development progress ===
| |
| The summary of the development progress can be found in [https://wiki.qt.io/PySide2_Development_Notes Development Notes by date]
| |
| | |
| === Pyside Development Progress Notes ===
| |
| | |
| The most current view of the progress can be found in Jira:
| |
| | |
| # [https://bugreports.qt.io/secure/IssueNavigator.jspa?mode=hide&requestId=17825 Unresolved issues] | |
| # [https://bugreports.qt.io/secure/IssueNavigator.jspa?mode=hide&requestId=18025 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:
| |
| * [[PySide2_Missing_Bindings|Missing PySide2 bindings]]
| |
| | |
| === Outstanding tasks for release ===
| |
| # Determine Pyside package number
| |
| # Ensure multi target packages can be created (long standing - reduced Python API usage )
| |
| # General Doc changes required for release
| |
| ## Getting started
| |
| ## Some examples documented
| |
| ## pyinstaller usage
| |
| ## Class documentation polish
| |
| ## 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.
| |
| | |
| # First time with Pyside (Document how to get started on this wiki)
| |
| # Testing Infrastructure
| |
| ## What has been done so far?
| |
| ## Qt CI support ([https://bugreports.qt.io/browse/PYSIDE-431 PYSIDE-431])
| |
| ### make test
| |
| ### cmake based build system (all repos)
| |
| ### pip installable Pyside
| |
| #### CI has to setup virtual Python environment
| |
| #### Use pip to install/build Pyside (release bundling)
| |
| | |
| # Future changes to PySide
| |
| ## Gaps (modules & API)
| |
| ### Identify the extent of the gaps by porting existing examples from Qt4 to Qt5 (done)
| |
| ### 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 ([https://bugreports.qt.io/browse/PYSIDE-323 PYSIDE-323])
| |
| ### QtQML support ([https://bugreports.qt.io/browse/PYSIDE-355 PYSIDE-355])
| |
| ## MyPy (type annotation - fully typed Python API)
| |
| ## General Python features and their adoption in PySide (e.g. Async I/O)
| |
| ## Creator and tooling
| |
| ### Fix QtC debugger to understand Python/C++ mixed internals
| |
| ## Documentation generation
| |
| ## Deployment of apps
| |
| ## Debugging support
| |
| | |
| # Must have tasks for first release
| |
| ## Packaging (e.g. pip deployment? )
| |
| ## Clarify Installer story
| |
| ## Documentation
| |
| ## Product placement decisions
| |
| ### Licensing
| |
| ### Naming
| |
| ### etc
| |
| ## Complete CI coverage
| |