Installing PySide for Python3

by

To get the latest PySide, install one of the official binary wheels from PyPI which includes a bundled Qt and is therefore fully portable.

  • For Qt5 – [Python 2.7 / Python >= 3.5]:

      pip install pyside2

  • For Qt6 – [Python >= 3.6]:

      pip install pyside6

The information presented in the section below relates to PySide-1.2/Qt4 and is no longer relevant unless you need to support legacy systems.

Firstly, it should be pointed out that PySide depends on Qt4, which is no longer officially supported (as of December 2015). In consequence, all development efforts are now focused on PySide2 and Qt5. According to this tracker issue, there are no plans for officially supporting PySide beyond Python-3.4 – mainly due to lack of resources and the difficulty of compiling on Windows. The current position (as of February 2017), seems to be summed up by this post:

This was last left as basically a wontfix, as one needs to modify both
Qt 4.8 and PySide sources to compile with the compiler used for Python
3.5 on Windows. Furthermore, Qt 4.8 is no longer supported, and PySide should not be used for new projects. PySide2, the next version, is the
future of Python and Qt, and supports Python 3.5. You can find out
more about it on the Qt Wiki.

Having said all that, there are several Linux distros that currently maintain PySide packages for Python-3.5 and/or Python-3.6. This usually only requires a small patch to the shiboken tool which generates the bindings (see the Arch Linux PKGBUILD, for example). In addition, there are Windows wheels available on Christoph Gohlke’s Unofficial Windows Binaries site. (I’m afraid I don’t know much about the situation for Mac, but I did find this wheel for Python-3.5).

So PySide itself is still currently compatible with Python-3.5 & 3.6 – but the official installers aren’t. However, if you’re willing to patch the toolchain or use unofficial binaries, this shouldn’t be a problem. Effectively, PySide and Qt4 are now frozen codebases, so unless there are some really radical changes made to Python, it “should” remain viable for several releases to come. The future is PySide2, though.

More Related Contents:

  1. How do I find the location of my Python site-packages directory?
  2. How do I install pip on macOS or OS X?
  3. Pip error: Microsoft Visual C++ 14.0 is required
  4. Installing SciPy with pip
  5. How to manually install a pypi module without pip/easy_install?
  6. How to install PIL with pip on Mac OS?
  7. How to set Python’s default version to 3.x on OS X? [duplicate]
  8. pip cannot uninstall : “It is a distutils installed project”
  9. Too many different Python versions on my system and causing problems
  10. QWidget does not draw background color
  11. SyntaxError: unexpected EOF while parsing
  12. String with ‘f’ prefix in python-3.6
  13. How to install xgboost package in python (windows platform)?
  14. How do I update a Python package?
  15. DistutilsOptionError: must supply either home or prefix/exec-prefix — not both
  16. Adding a data file in Pyinstaller using the onefile option
  17. “RuntimeError: Make sure the Graphviz executables are on your system’s path” after installing Graphviz 2.38
  18. Combine –user with –prefix error with setup.py install
  19. Tensorflow r1.0 : could not a find a version that satisfies the requirement tensorflow
  20. Nested f-strings
  21. How do I install Python libraries in wheel format?
  22. Installing lapack for numpy
  23. Why python executable opens new window instance when function by multiprocessing module is called on windows
  24. PySide2 QMainWindow loaded from ui file not triggering window events
  25. Python and F-Strings explanation
  26. how to successfully install pyproj and geopandas?
  27. How to signal slots in a GUI from a different process?
  28. How to install Python packages for Spyder
  29. Create an abstract Enum class
  30. Upgrade Python to 2.6 on Mac

Leave a Comment