![]() This was particularly noticeable following the release of Qt 5 - the Qt5 version of PyQt (PyQt5) was available from mid-2016, while the first stable release of PySide2 was 2 years later. The two interfaces were comparable at first but PySide ultimately development lagged behind PyQt. Unable to come to agreement with Riverbank (who would lose money from this, so fair enough) they then released their own bindings as PySide (also, fair enough).Įdit: it's called PySide because "side" is Finnish for "binder" - thanks to Renato Araujo Oliveira Filho in the comments. ![]() Back in 2009 Nokia, who owned the Qt toolkit at the time, wanted to have Python bindings for Qt available under the LGPL license (like Qt itself). for a very long time - supporting versions of Qt going back to 2.x. ![]() PyQt has been developed by Phil Thompson of Riverbank Computing Ltd. By the end you should be comfortable re-using code examples from both PyQt5 and PySide2 tutorials to build your apps, regardless of which package you're using yourself. In this short guide I'll run through why exactly this is, whether you need to care (spoiler: you really don't), what the few differences are and how to work around them. ![]() If you start building Python application with Qt5 you'll soon discover that there are in fact two packages which you can use to do this - PyQt5 and PySide2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |