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

List:       pykde
Subject:    Re: [PyKDE] QString in PyQt4 - Request for Comments
From:       "Giovanni Bajo" <rasky () develer ! com>
Date:       2005-10-21 9:35:55
Message-ID: 01ce01c5d622$d616d5a0$bf03030a () trilan
[Download RAW message or body]

Phil Thompson <phil@riverbankcomputing.co.uk> wrote:

> I'm completely open to making the existing API more Pythonic - this is the
> time to do it. For example, I did casually float the idea of not using C++
> types in signal signatures in a previous post - but nobody bit.

I didn't, because of the reasons explained previously: I believe it would
just cause more confusion, in the current PyQt design. It's just too handy
to go looking to the signature in the Qt Assistant and use it. I don't want
to go check in two different manuals. Until now, PyQt's goal has been to
adhere as much as possible to Qt, to not confuse existing Qt users and I
think it's a noble goal. I also understand that this is not ideal for a
Python-only programmer.
-- 
Giovanni Bajo

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]