

Against: Does not look native, less popular than PyQt/PySide. In favour: Easy to set up, since it’s pre-installed with Python.

In favour: Less restrictive licensing (LGPL instead of GPL). Pyside: Another framework for bindings for Qt.Since my project was open-source anyway and uses the MIT license, this was fine by me. That means that if you distribute the Qt Gui Toolkit as part of your application binary, your program must also be licensed under a GPL-compatible license. Something that you should consider about PyQt5 is that licensed under the GPL 3.0 license. Creating a package in an expected file formatįor creating a GUI in Python, I chose to use PyQt5, a framework that provides Python bindings for the great C++ Qt framework.Turning the project into a self-contained executable file.This is the first part of the series where I write about things I learned while writing a desktop app. Creating a file that users could download in an expected file format.Turning it into a self-contained executable file that does not rely on having Python or other dependencies being installed.Looking native, presenting a GUI when clicked.While I was working on the Quaver Lyrics Finder project (it’s my first time writing Python, please be gentle), I wanted to make it into an easy-to-use program that most people to use.
