Question 1

How to switch from PyQt5 to PySide6 with QtPy?

Accepted Answer

Set the QT_API environment variable to 'pyside6' before launching your app. QtPy will redirect imports automatically, allowing the same code to run without changes, as per the environment configuration details.

Question 2

QtPy or direct PyQt6 for a new project?

Accepted Answer

Use direct PyQt6 if you're certain about sticking with one binding and don't need cross-compatibility. QtPy is better for projects expecting future binding switches or requiring multi-binding support, as it abstracts differences.

Question 3

Does QtPy work with QtQuick or QML?

Accepted Answer

QtPy supports core Qt modules following the Qt5 layout, but some advanced modules like QtQuick may require careful testing. The compat module focuses on helpers for QFileDialog and SIP/Shiboken, not all Qt features.

Question 4

How to set up MyPy type checking with QtPy?

Accepted Answer

Run 'qtpy mypy-args' to generate CLI arguments (e.g., --always-true=PYQT5) and inject them into your MyPy command. This ensures type definitions align with the selected binding, as described in the type checker integration section.

Question 5

What if multiple Qt bindings are installed?

Accepted Answer

QtPy defaults to PyQt5 unless QT_API is set. You can control this via the environment variable to specify the binding, preventing ambiguity in multi-binding environments.

Question 6

Can I use QtPy with conda?

Accepted Answer

Yes, QtPy is available on conda-forge, and the README shows it's tested with conda installations across different bindings and Python versions. Ensure the desired binding is installed in the same conda environment.

qtpy

What is qtpy?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions