py(Qt|KDE) and KDE CVS

Adriaan de Groot adridg at
Sun Mar 21 11:16:00 GMT 2004

Hash: SHA1

(Forwarded message from Simon Edwards, the guy who would want to maintain the 
python bindings in a visible place (more visible than kdebindings, since that 
module has code ranging from totally deprecated (SWIG) to fairly recent and 
possibly maintained (korundum)))

I've been discussing with the PyQt/PyKDE developers and some KDE devs about 
this. What we would like to see is a new module of some kind that would be 
released as part of each KDE release. This module would act a lot like 
qt-copy and hold a "ready to go" copy of all of the stuff necessary to build 
and install the PyQt and PyKDE bindings. I would volunteer to act as 
maintainer in this case.

The whole goal of this is to provide and maintain a stable platform where 
people can choose to develop 3rd party applications using Python on KDE. 
Currently developers are reluctant to develop using Python on KDE, not for 
technical reasons, but for organisational and deployments reasons. They need 
the assurance that their end users can run their applications without too 
much difficulty, also the assurance that "python on kde" will always be 
readily available from KDE release to KDE release.

What are kde-core-devel's thoughts on this?

- -- 
Simon Edwards             | Guarddog Firewall
simon at       |
Nijmegen, The Netherlands | "ZooTV? You made the right choice."
Version: GnuPG v1.2.4 (FreeBSD)


More information about the kde-core-devel mailing list