Skip to content

Conversation

@Sakth1
Copy link
Contributor

@Sakth1 Sakth1 commented Jan 8, 2026

Checklist

  • One link per Pull Request
  • PR title format: Add project-name
  • 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)

  • 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.

Sakth1 added 3 commits January 8, 2026 15:04
Clarified the description of PySide in the README.
Clarified the description of PySide in the README.
@vinta vinta merged commit 36b8519 into vinta:master Jan 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants