Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for Python
  4. PySide 2 vs PyQt maturity

PySide 2 vs PyQt maturity

Scheduled Pinned Locked Moved Unsolved Qt for Python
3 Posts 2 Posters 2.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    JonB
    wrote on 19 Jul 2019, 07:31 last edited by JonB
    #1

    As of today (50 years after Moon Landing), how "mature"/"comprehensive" is Qt's PySide 2 offering, compared to PyQt?

    When I started out on Qt 2 or 3 years ago, I looked at PySide and there were whole swathes of Qt functionality which were simply not implemented (don't ask me now which).

    I use PyQt, which is mature & comprehensive. It receives nightly fixes where necessary. The innards are complex, and sometimes one needs to understand them to achieve something.

    I would be tempted to move to PySide 2 --- either for large existing project or perhaps only on new projects --- not least because of the licensing issue. But cannot do that unless it is now fully able to cope with everything PyQt can.

    Does anyone perhaps have any experience of both, or recent stories about migrating from PyQt to PySide?

    1 Reply Last reply
    0
    • J Offline
      J Offline
      JonB
      wrote on 19 Jul 2019, 14:06 last edited by
      #2

      @Denni-0
      Hi, thanks for commenting. But I must correct a couple of your statements.

      Yes, it is the fact that (open source) PySide 2 is LGPL, like Qt itself, whereas PyQt is GPL, that is a big consideration for most of us when picking a Qt for Python brand.

      Don't say "PySide 2 is a sticky wicket because it's open-source". Unless you have purchased a paid license for Qt, most people in this forum are using the Open Source version of Qt (for C++). So PySide 2 being open source is neither better/worse/stickier than the Qt it goes with.

      As for your

      Use pyqt5 as it makes no sense to add a third party into the mix

      in fact it is PyQt which is already the "third party" added into the mix. PyQt is from Riverbank, a third-party, whereas PySide 2 is from the Qt company, just like Qt. So it is PySide 2 which is not the "third-party" here. If one applied your argument here --- which does have a certain merit --- it would dictate the opposite of what you say, i.e. use PySide 2 rather than PyQt.

      You said:

      pyqt5 (supplied by the makers of Qt5 if my information is straight)

      No, you have it the wrong way round. PySide is supplied by the Qt company, not PyQt.

      1 Reply Last reply
      0
      • J Offline
        J Offline
        JonB
        wrote on 19 Jul 2019, 14:33 last edited by JonB
        #3

        @Denni-0
        Please yourself as to whether you call "pyqt5 (a child product of Qt5)". To me it is not. It is a third-party who chose to develop it.

        PyQt is "futher advanced" than PySide because it's had a (much) longer development. Until recently, PyQt was the de facto standard for Qt in Python, and you'll see a lot more questions/answers out there compared to PySide. It is only recently (last year? I forget) that PySide went to PySide 2, and only that can hope to rival PyQt, PySide "1" was very incomplete.

        1 Reply Last reply
        0

        3/3

        19 Jul 2019, 14:33

        • Login

        • Login or register to search.
        3 out of 3
        • First post
          3/3
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved