Pyside6 is used in Python projects. Python bindings for the Qt cross-platform application and UI framework It has 4 direct runtime dependencies. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
Python bindings for the Qt cross-platform application and UI framework
pyside6 declares 4 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, pyside6 can pull in further packages through its dependency tree. PyDeps resolves the entire chain from PyPI and deps.dev so you can see every transitive (nested) dependency of pyside6, expand any node on demand, and understand the full set of code that ships when you run pip install pyside6.
PyDeps checks pyside6 and every package in its dependency tree against the OSV vulnerability database in real time. For each CVE you can see the severity, the affected version ranges, and the first fixed version, so you know exactly which pyside6 version is safe to install before you ship.
pyside6 is distributed under the LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole pyside6 install, not just the top-level package.
Install from PyPI with pip install pyside6. For offline or air-gapped environments, PyDeps can download pyside6 together with every resolved dependency as wheel files in a single bundle, matched to your target Python version and operating system.
Switch to the dependents view to see the reverse dependencies of pyside6 — the PyPI packages that list pyside6 as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.