Hi,
I just thought I might give a short overview about our current plans on
PySide. We're at the moment very much focusing on the Shiboken work,
i.e. replacing Boost.Python with a new, much more efficient binding
generation architecture. This work will take still some time, but I'm
quite confident that Boost.Python will have been replaced by the end of
the year, very probably somewhat earlier than that. Parallel to that
work, we'll also do the Qt 4.6 porting. Once these items have been
completed, we'll probably carry on with the Python 3 porting. (We won't
try to port the Boost.Python based stuff to Python 3, but instead work
only on Shiboken there.)
With all of this in mind, I believe it would be now a perfect time to
begin planning any backwards-incompatible changes to PySide, as the
Python 3 transition would be the perfect instant to incorporate them.
So, start discussing those PSEP ideas! ;-)
As for the Python 2.x PySide, we're of course still more or less at the
PyQt 4.4 level regarding the Pythonic features. I'm not sure whether and
what we should do about it. Basically, we could let it be as is, mimic
the PyQt 4.5 functionality, or invent something of our own. I'd be also
happy to hear your opinions on this one.
Cheers,
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
