Qt for Python
- 1 Qt for Python
- 2 Getting Started
- 3 What does Qt for Python look like?
- 4 Community
- 5 Development Status
- 6 Frequently Asked Questions
- 7 Known issues
- 8 Contributing to the Qt for Python Wiki
Qt for Python
The Qt for Python project aims to provide a complete port of the PySide module to Qt 5. 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 ).
The module was released mid June as a Technical Preview (supporting Qt 5.11).
This wiki page tracks the progress of the Qt for Python project development and provides further information concerning the effort.
Qt for Python is available under GPL, LGPL and commercial license.
- Official documentation (snapshot)
- Getting started guide for macOS, Windows and Linux (Download and Install/Build)
- Development: Getting started
- Reporting Bugs to report any issue.
- CodeReview and PySide2 open patches
- Git repository (5.11 branch is the branch currently worked on for PySide2)
What does Qt for Python look like?
1 import sys 2 from PySide2.QtWidgets import QApplication, QLabel 3 4 if __name__ == "__main__": 5 app = QApplication(sys.argv) 6 label = QLabel("Hello World") 7 label.show() 8 sys.exit(app.exec_())
More examples can be found in the project's repository inside the examples directory.
- Official IRC channel on FreeNode #qt-pyside
- Official Mailing list
- Gitter: gitter.im/PySide/pyside2
- Have an idea? share it with us!
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:
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
- Determine PySide2 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/
Frequently Asked Questions
- Q: PySide? Qt for Python? what is the name?
- A: The name of the project is Qt for Python and the name of the module is PySide2.
- Q: Why PySide2 and not just PySide?
- A: Since PySide was developed for Qt4, when the port was made to support Qt5, the name was changed to PySide2 to imply that it was a newer version.
- Q: Where I can find information about the old PySide project?
- A: The old wiki page of the project is available on PySide, but the project is deprecated and there is no official support for it. We highly recommend not to use it.
- Q: My project is using PySide, how hard would it be to adapt it to PySide2?
- A: The changes are the same as between Qt4 and Qt5, and for PySide users it mostly means adapting the import statements since many classes were moved from QtGui to QtWidgets.
- Qt 5 is highly compatible with Qt 4. It is possible for developers of Qt 4 applications to seamlessly move to Qt 5 with their current functionality and gradually develop new things, leveraging all the great items Qt 5 makes possible.
- Q: Does PySide2 support Android and iOS development / deployment?
- At the moment there is no support for mobile platforms. It will be looked into some time in the future.
Contributing to the Qt for Python Wiki
This Wiki is a community area where you can easily contribute, and which may contain rapidly changing information. Please put any wiki pages related to Qt for Python into the "QtForPython" category by adding the following text to the top of the page:
[[Category:Qt for Python]]
When creating a new wiki page, please start the name with the prefix "Qt_for_Python/", so all the wiki page names will have the same structure and breadcrumbs are generated for easier navigation.