Explain:
Qt is the standard GUI framework. PySide has similar internal APIs with its c++ counterpart. If you have the Qt license for using the Qt framework, I'm pretty sure you can also use PySide commercially (Although give the licensing a read, I don't really understand some licensing usages).
I feel like both of the project should be mentioned since one was the initial binding and most people know it for and the other is the official binding of the Qt framework. The final call is on your hand though.
How It Differs
Licensing is different from PyQt (as I mentioned like a thousand times). This uses 'signal' and 'slot' while PyQt uses 'pyqtsignal' and 'pyqtslot' for UI signal and slot functionality.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/vinta/awesome-python/pull/2839
**Author:** [@Sakth1](https://github.com/Sakth1)
**Created:** 1/8/2026
**Status:** ✅ Merged
**Merged:** 1/9/2026
**Merged by:** [@vinta](https://github.com/vinta)
**Base:** `master` ← **Head:** `pyside`
---
### 📝 Commits (4)
- [`1d63278`](https://github.com/vinta/awesome-python/commit/1d6327894789fd5f50391f25a39fe537839265ee) added pyside to gui
- [`87f11bc`](https://github.com/vinta/awesome-python/commit/87f11bcb724f6db6d846ba8cf6332a76011c147a) Update PySide description in README
- [`3d5d1c8`](https://github.com/vinta/awesome-python/commit/3d5d1c8cb9a7d97c9812c05f6b1e187039d457c6) Update PySide description for clarity
- [`e2405a6`](https://github.com/vinta/awesome-python/commit/e2405a687dab695754fe73d09d25858a3fa2b13d) Merge branch 'master' into pyside
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
## Checklist
- [x] One link per Pull Request
- [x] PR title format: `Add project-name`
- [x] Entry format: `* [project-name](url) - Description ending with period.`
- [ ] Description is concise (no mention of "Python")
## Why This Project Is Awesome
Which criterion does it meet? (pick one)
- [x] **Industry Standard** - The go-to tool for a specific use case
- [ ] **Rising Star** - 5,000+ stars in <2 years, significant adoption
- [ ] **Hidden Gem** - Exceptional quality, solves niche problems elegantly
Explain:
Qt is the standard GUI framework. PySide has similar internal APIs with its c++ counterpart. If you have the Qt license for using the Qt framework, I'm pretty sure you can also use PySide commercially (Although give the licensing a read, I don't really understand some licensing usages).
I feel like both of the project should be mentioned since one was the initial binding and most people know it for and the other is the official binding of the Qt framework. The final call is on your hand though.
## How It Differs
Licensing is different from PyQt (as I mentioned like a thousand times). This uses 'signal' and 'slot' while PyQt uses 'pyqtsignal' and 'pyqtslot' for UI signal and slot functionality.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/vinta/awesome-python/pull/2839
Author: @Sakth1
Created: 1/8/2026
Status: ✅ Merged
Merged: 1/9/2026
Merged by: @vinta
Base:
master← Head:pyside📝 Commits (4)
1d63278added pyside to gui87f11bcUpdate PySide description in README3d5d1c8Update PySide description for claritye2405a6Merge branch 'master' into pyside📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Checklist
Add project-name* [project-name](url) - Description ending with period.Why This Project Is Awesome
Which criterion does it meet? (pick one)
Explain:
Qt is the standard GUI framework. PySide has similar internal APIs with its c++ counterpart. If you have the Qt license for using the Qt framework, I'm pretty sure you can also use PySide commercially (Although give the licensing a read, I don't really understand some licensing usages).
I feel like both of the project should be mentioned since one was the initial binding and most people know it for and the other is the official binding of the Qt framework. The final call is on your hand though.
How It Differs
Licensing is different from PyQt (as I mentioned like a thousand times). This uses 'signal' and 'slot' while PyQt uses 'pyqtsignal' and 'pyqtslot' for UI signal and slot functionality.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.