Excellent video. Clearly explained, with genuinely helpful clarifications, you've obviously put thought into this rather than cribbing points. Now I'm keen to watch other of your videos too 👍
Good video. I have quite knowledge and experience in pyqt & pyside on both Windows and MacOs and still found your presentation useful. Please keep up the good work!
Quite good video, but in my opinion two very important questions should be considered, too: Which one has the larger user base? And how easy is it to contribute (e.g. bugs, code, documentation). Both affects how up-to-date each software stays when it is already released. While a big user base might faster stumble uppon bugs in the software, and maybe provide workarounds or solutions, a project that allows easy contribution might even have faster provisioning of bug fixes. From my daily use, I would always go with pyqt in early development. And then, if really needed switch to pyside for releasing.
Thanks for informative video. But I'd like to point that Qt is not just a framework for building GUIs. It's a framework that contains tools for building GUIs but also much more. You can write command line tools, daemons and embedded software with it also nicely. You could compare it to boost library which does lot of same but doesn't have a GUI module.
How to use Asyncio with pyside6? I have a GUI designed by pyside6 (and Qt), behind the GUI I have intensive serial communication done by Pyserial and asyncio....can I share the same event loop required by GUI and asyncio?
Hi, I am from India, I want to use Pyside6 for my Commercial Application software for Accounting. I will use Pyside6's Text Entry, Labels Etc. I will not change the code for this labels and text entry etc. I will use Ditto as available. Can i Use as LGPL? What will be my obligation? I do not want to show my code to end user
I was wondering - even if I want to distribute my software, since it is python scripts, how can I hide the code from users? Isn't python code always source code?
@@pixeled_violence ok and we she said "share the code with the app user"... what does she mean? because If I give my client a .exe how this pearson is to have the code? I am new using PyQt5 and maybe this is an answer well discuss before
@@_isDevI think when you use a free pyqt then you gave to share the source code with the user, but if you buy a license from pyqt you can hide your code.
I don't understand something: What do you mean by give my code to my client? how people from PyQt5 knows I am going to sell a gui built using this framework? If I create a .exe to install the gui in the client's computer... I don't really understand
Technically they do not know that you've used their code. However, even if you package your Python code into an .exe or .dmg it is still possible to de-compile your binary and see what symbols (function, constants, shared libraries ...) were used in it. That's where it is possible to deduce whether you used PyQT or not and if it is determined that you did, you'll be in violation of their license and they'll be able to win in court against you. If that happens, you'll be liable for breach of license agreement and would have to pay them damages. All in all, if you are developing software as a business, the legal risk isn't worth it.
It does make sense in quite a few scenarios. For example, selling technical software in business to business sells. Another is embeded. Look at the about info on any modern LG TV. It's actually running quite a lot of open source software under the LGPL.
If people are going to commit to anyone of these to options, note there is no substantive community for working with these two frameworks. And absolutely zero for working with the QML language. (Qt is not QML) You’ll pretty much have a pretty interface but connecting to a database or doing serial communications, you’ll be on your own. It should come with a warning, that the developers of the framework don’t respect the time commitment of folks new to the framework. But this would become obvious when you see that no one is really offering any tutorials on it. You can take your chances with Qt but not the QML part.
@egedesolomon7454 So far, it's been my experience working with Pyside6 using QML as it pertains to community support, they're both the same thing. It's really the import statements are worded differently. And after spending time using QML, there has yet a problem or feature implementation that I haven't been able to solve, doing Google searches, StackOverflow or the Documentation.
@michaelosajeh4111 Yes. That's what I did. I mostly utilized PySide signal slots and properties to connect to qml. But for tasks lilke serial communication, threading, and database stuff, I leaned on the Python community's robust support. A.I. (Codium) is also a good tool for offering up suggestions on the Pyside6 libraries, but it also struggles. But it rocks for pure python and cpp work. I use Qml because it gives me the opportunity to code in a Model, View, Controller, OOP style. Plus QML is really straightforward and tidy..
![PyQt vs. PySide: Differences, Similarities, and Licenses [2022]](/img/logo.svg){kind=logo}
