Getting back into PyQt and not loving it.

From	Michael Torrie <torriem@gmail.com>
Newsgroups	comp.lang.python
Subject	Getting back into PyQt and not loving it.
Date	2016-06-26 15:45 -0600
Message-ID	<mailman.15.1466977505.2358.python-list@python.org> (permalink)
References	<7583145f-fa2a-6846-3cd9-9814c7006fdd@gmail.com>

Show all headers | View raw

I'm starting to question the advice I gave not long ago to for new users
to consider the Qt toolkit with Python.

I just did a little project porting a simple graphical user interface
from GTK+ to Qt (PyQt4 for now as that's what I have installed).  For
the most part it worked out pretty well.  It's been a while since I used
PyQt or PySide, and I had forgotten what a horrid Python experience Qt
really is, at least in PyQt4.  Maybe the bindings for Qt5 are better...
I'll be working with them next as I convert my working code.

Qt's a fantastic toolkit, and the most mature of any of them, and the
most portable, but man the bindings are not Pythonic at all. PyQt does
not seem to hide the C++-isms at all from the programmer.  I am
constantly wrapping things up in Qt classes like QRect, QPoint, QSize,
etc, when really a python Tuple would have sufficed.  All the data
structures are wrapped in Qt C++ classes, so you end up writing what is
really idiomatic C++ code using Python syntax. Not the best way to code
Python!  Implementing signals in a class, too, reminds you strongly that
you're working with C++ as you have to construct their method signatures
using types that map back into C++.

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Getting back into PyQt and not loving it. Michael Torrie <torriem@gmail.com> - 2016-06-26 15:45 -0600
  Re: Getting back into PyQt and not loving it. llanitedave <llanitedave@birdandflower.com> - 2016-06-26 18:05 -0700
    Re: Getting back into PyQt and not loving it. Rustom Mody <rustompmody@gmail.com> - 2016-06-26 18:34 -0700
    Re: Getting back into PyQt and not loving it. MRAB <python@mrabarnett.plus.com> - 2016-06-27 03:12 +0100
      Re: Getting back into PyQt and not loving it. Mark Summerfield <list@qtrac.plus.com> - 2016-06-27 00:33 -0700
    Re: Getting back into PyQt and not loving it. Michael Torrie <torriem@gmail.com> - 2016-06-26 20:41 -0600
      Re: Getting back into PyQt and not loving it. John Ladasky <john_ladasky@sbcglobal.net> - 2016-06-26 23:15 -0700
        Re: Getting back into PyQt and not loving it. Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-26 23:44 -0700
          Re: Getting back into PyQt and not loving it. Michael Torrie <torriem@gmail.com> - 2016-06-27 09:11 -0600
        Re: Getting back into PyQt and not loving it. llanitedave <llanitedave@birdandflower.com> - 2016-06-27 10:23 -0700
    Re: Getting back into PyQt and not loving it. Ethan Furman <ethan@stoneleaf.us> - 2016-06-27 16:00 -0700
  Re: Getting back into PyQt and not loving it. lorenzo.gatti@gmail.com - 2016-06-27 00:27 -0700
  Re: Getting back into PyQt and not loving it. codewizard@gmail.com - 2016-06-27 13:14 -0700
    Re: Getting back into PyQt and not loving it. Michael Torrie <torriem@gmail.com> - 2016-06-27 18:26 -0600
    Re: Getting back into PyQt and not loving it. Sibylle Koczian <nulla.epistola@web.de> - 2016-07-02 12:08 +0200
    Re: Getting back into PyQt and not loving it. Sibylle Koczian <nulla.epistola@web.de> - 2016-07-02 12:08 +0200

csiph-web