Frequently Asked Questions#

When did The Qt Company adopt PySide?

In April 2016 The Qt Company decided to properly support the port. For more information, see!topic/pyside-dev/pqwzngAGLWE.

Why use PySide6 and not PySide, or PySide2?

The PySide Python module was developed for Qt 4 and PySide2 adapts the same for Qt 5. From Qt 6 onwards, the module name changes to PySide6, indicating the Qt version it supports.

Where I can find information about the old PySide project?

The project’s old wiki page is available on PySide, but the project is now deprecated and not supported.

There are three wheels (pyside6, shiboken6, and shiboken6_generator), what’s the difference?

Before the official release, everything was in one big wheel, so it made sense to split these into separate wheels, each for the major projects currently in development:

  • pyside6: contains all the PySide6 modules to use the Qt framework; also depends on the shiboken6 module.

  • shiboken6: contains the shiboken6 module with helper functions for PySide6.

  • shiboken6_generator: contains the generator binary that can work with a C++ project and a typesystem to generate Python bindings. If you want to generate bindings for a Qt/C++ project, there won’t be any linking to the Qt shared libraries; you need to do this by hand. We recommend building PySide6 from scratch to have everything properly linked.

Why is the shiboken6_generator not installed automatically?

It’s not necessary to install the shiboken6_generator to use PySide6. The package is a result of the wheel splitting process. To use the generator, it’s recommended to build it from scratch to have the proper Qt linking.