[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] Fwd: PyQt documentation where PyQt function is not same as Qt C++ function
From:       Florian Bruhin <me () the-compiler ! org>
Date:       2017-11-28 17:02:28
Message-ID: 20171128170228.rdqzjjzzvy3eu2v2 () hooch ! localdomain
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tue, Nov 28, 2017 at 04:53:18PM +0000, J Barchan wrote:
> Purely OOI, do we know whether the automated "Qt C++ to PyQt Python
> converter" recognises this signature pattern (i.e. non-const * or &) and
> automatically generates a tuple-return for it?  Somehow I doubt it (too
> difficult, too reliant on C++ signature using const everywhere correctly),
> so I'm thinking these tuple-returns are handled by the author manually?

PyQt has binding definition files (.sip files), which are basically C++ header
files (.h) with additional annotations. For those cases, there's an /Out/ or
/In,Out/ annotation in it.

Those are generated in a half-automated way as far as I'm aware, see
https://dot.kde.org/2006/08/09/phil-thompson-talks-about-pyqt

(Unless something changed about that in the meantime, which is something only
Phil can answer :D)

Florian

-- 
https://www.qutebrowser.org  | me@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
         I love long mails!  | https://email.is-not-s.ms/

["signature.asc" (application/pgp-signature)]
[Attachment #6 (text/plain)]

_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt

[prev in list] [next in list] [prev in thread] [next in thread]