Unoffical PySide2 standalone wheels for Windows.
Download the standalone wheels
Releases contain built PySide2 wheels.
If you wish to check the wheels produced by e.g. a PR, see the AppVeyor build history, navigate to a build and download the attached artifacts.
How does this work?
AppVeyor runs virtual Windows machines which are equipped with preinstalled software, in which e.g. Python and Qt are already installed and available. Using a build matrix, multiple configurations can be defined and run the same commands as stipulated in the
appveyor.yml file. Because of this, PySide2 builds are limited to whatever versions of e.g. Python and Qt are available at AppVeyor (which to date hasn't caused any problems).
The built PySide2 wheels are registered as artifacts and are attached to each AppVeyor build (see the "Artifacts" tab under each job's build. This also includes builds initiated by pull requests.
git tag initiated the AppVeyor job, a Github release is also peformed. All built wheels are deployed and attached to the Github release.
Rolling builds are enabled for this project in AppVeyor, which means that queued up jobs are cancelled if a new job is initiated.
A note on Upstream issues
All upstream issues should be reported in the official PySide issue tracker.
Note: PRs attempting to fix upstream fixes will not be accepted. Please send your PR upstream instead.
Ask questions in the PySide/PySide2 gitter
If you have any general questions, please check out the PySide2 Gitter community. If you prefer IRC, check out
#qt-pyside on irc.freenode.net.