[PyKDE] Why are the python bindings delivered with KDE so old?

[Simon Edwards]

On Wednesday 24 January 2007 00:12, Serge Weinstock wrote:
> Thanks you for your explanations, I didn't know that the KDE 3.x series
> was now in maintenance.

Effort in the KDE community has been concentrated on KDE 4 for quite some time 
now. KDE 4 is due this year, while KDE 3 is (mostly) getting bug fixes and 
maintenance releases.

> I must confess that I'm surprised by the recommendation of using PyQt4
> for new KDE applications as to my knowledge neither the KDE4 API has
> been stabilized, nor a public release of the Python bindings for KDE4
> has been released.

True. The trick is that it doesn't make too much sense to develop on an old 
platform, and the KDE API itself needs testing and feedback before release. 
(read: people using it). PyKDE on KDE 4 should be available for initial use 
and testing, real soon now. Of course if you have a KDE3 application that you 
want to release before KDE4, then that's the way it is. But moving to Qt / 
KDE 4 should be a high priority.

We want to have as many applications available as possible when KDE 4 is 
released.

> Personally, I can't use only PyQt for my current project as I don't want
> to rewrite the huge amount of useful code found in the KDE libraries.

I don't want you to either. :-)

> This is very good news to know that pyKDE4 will be developed directly
> inside the KDE project.  

People who are following KDE4 development will be able to track PyKDE 4 
development soon once it hits KDE's SVN. (Jim is still working on an initial 
version/port).

cheers,

-- 
Simon Edwards             | KDE-NL, Guidance tools, Guarddog Firewall
simon at simonzone.com       | http://www.simonzone.com/software/
Nijmegen, The Netherlands | "ZooTV? You made the right choice."