On 2009-10-28, Renato Araujo Oliveira Filho wrote:
> Hi all,
>
> I didn't see any problems with new PyQt signal/slot implementation,
> but like I talked before I love the way the signal and slot works in
> C# implementation. And I think we can implement both only adding the
> operator "+=" and "-=" in slot and signal objects.
>
> Another point is, we need take care of follow PyQt api, to no create a
> eternal link between PySide and PyQt. This can leave the users always
> wait for compatibilities, and this will make all this great ideas of
> PEP's unnecessary. Then we need keep clear, PySide not will be
> compatible with PyQt in the future.
Are you saying that you _plan_ to make PySide incompatible with PyQt in
the future?
Right now there are lots of PyQt developers (open & closed source); how
many I don't know but my guess is at least tens of thousands. And how
many PySide developers are there; my guess is low hundreds...
I hope that PySide matches the PyQt API for many years---ideally for at
least three years _after_ PySide becomes the most widely used
implementation (if that ever happens;-)
After all, if people can easily switch between them it can only be to
PySide's advantage (since most people use PyQt); only if PySide becomes
dominant would it make sense to become incompatible---and only then if
trying to kill PyQt was more important than supporting users.
my 2c
--
Mark Summerfield, Qtrac Ltd, www.qtrac.eu
C++, Python, Qt, PyQt - training and consultancy
"Programming in Python 3 (Second Edition)" - ISBN 0321680561
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
