Hi @IoT welcome for the forum!
I’m reading the article, googling for an hour and still don’t understand the licensing model. Sorry new to Qt and would appreciate if you make it clear for me.
Don’t worry, this stuff can be hard to get your head around. There is a bit of information on licensing in this article but I’ll break it down a bit more for your specific situation. But bear in mind, I’m not a lawyer
- PyQt5 is GPL licensed, PySide2 is LGPL licensed.
- Both licenses have no effect on whether you can sell your software commercially. You can sell GPL licensed software and LGPL licensed software.
- Both licenses may require you to share source code in specific circumstances, but LGPL is unlikely to apply to a Python project.
For applications built with PyQt5 (GPL) if you distribute the software you must also make the source code of your software available to users (this doesn’t mean making it publicly available, you can send it on request).
For applications build with PySide2 (LGPL) if you distribute the software you don’t need to share the source of your application to your users. The one situation where you do need to share source when you modify the source of the LGPL library itself. You normally won’t be doing this while building Python apps.
The following part is also relevant –
In fact, the access to file system will be locked for them so all they see is a GUI which they can interact with.
I assume you’re not locking your users PC’s file system (!) so this is an embedded system? The GPLv3 (which PyQt5 is) has specific requirements for allowing end-users to modify/update the software on devices and receiving access to the source. If your device prevents this, I believe the GPLv3 would be a no-go anyway.
Based on what you’ve described your options are PySide2 (LGPL), or PyQt5 with a Riverbank commercial license.