Distribute a PySide6 app on Windows

Scope

This draft addresses a direct, native PySide6 GUI application targeting Windows 11 x64. The local release estate uses PySide6 as the Qt backend beneath pywebview, so it provides related packaging evidence but does not reproduce a standalone native PySide6 application.

The estate’s --onedir choice is tied to PolyForm Noncommercial/Internal Use distributions where bundled LGPL Qt and other LGPL libraries must remain replaceable by end users. It is not a general layout preference.

Answer

Treat direct PySide6 distribution as a separate packaging validation path. Qt for Python documents packaging tooling, while the local evidence demonstrates only that PySide6 is collected in a PyInstaller --onedir build for a pywebview application where the estate’s LGPL replaceability requirement applies. Start from Qt for Python’s packaging guidance, then verify your direct PySide6 executable, resources, plugins, installer, and update path together.

Decision path

If your UI is pywebview hosted on the Qt backend, follow pywebview Windows distribution.
If the application is directly built with PySide6 widgets or QML, use Qt for Python’s packaging guidance and test your own output.
If dependency licensing requires users to replace or relink bundled libraries, evaluate the mapped --onedir route. Only that conditional route is represented in the local evidence. Read one-file versus one-folder.
If you need a conventional installer after application validation, use the installer route as an implementation reference, not as proof for a native PySide6 application.

Production evidence

Simple Account Balancer’s requirements pin PySide6 with pywebview and PyInstaller. Its README identifies pywebview on the Qt backend. Simple UNA Log Viewer’s build script explicitly collects PySide6 in the --onedir bundle used where the estate’s LGPL replaceability requirement applies.

Unsupported or external outcomes

A native standalone PySide6 release is viable but not reproduced here.
--onefile was not chosen or reproduced for the mapped PolyForm route. Other license and distribution models require their own analysis and testing.
Authenticode signing and its certificate lifecycle are not reproduced.
Store or MSIX is external. Store distribution may be viable but is not reproduced here.
General WinGet acceptance is external.
Neither a checksum nor provenance establishes malware safety or SmartScreen reputation.
This is not legal advice. Layout alone does not fulfill all license obligations; notices, source or offer requirements, and the actual dependency and license versions still matter.

Source ledger