faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
New Python Libraries
by Evan "JabberWokky" E. on Tuesday 17/Sep/2002, @09:43
|
Hurm. Python libraries for Qt and KDE would be much appreciated. Right now, it takes me about 12 hours to compile them (via the sip library), but much more importantly, not only have I never gotten PyKDE working right. In addition, from browsing mailing lists, many people have to disable core parts of the library to get it to compile. I also have never gotten any binary installs to work, and from reading about it, it appears that the libraries may be somehow minor version specific (!!).
Disclaimer: I tilt at the libraries every couple months. I just subscribed to the PyKDE mailing list to make a serious run at getting everything working. My current problem is that calls don't seem to line up between what KDE provides and what sip generates. Odd.
(Incidently, I have an urge to poke at Smoke now and see if I can get it to create a Zend library just to write a couple dozen KDE apps in PHP to tweak the people on the dot who say PHP is just a web scripting language)
--
Evan |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: New Python Libraries
by Anonymous on Tuesday 17/Sep/2002, @09:57
|
<quote>My current problem is that calls don't seem to line up between what KDE provides and what sip generates. Odd.</quote>
Maybe you missed a few spaces. Also check for tabs. Mixing them with spaces is lethal in Python!
|
[
Reply To This | View ]
|
Re: New Python Libraries
by Evan "JabberWokky" E. on Tuesday 17/Sep/2002, @10:44
|
Heh. I'm talking about when I compile PyKDE - the autogenerated .cpp files are making KDE calls that don't exist or are malformed. Nor am I alone (although this particular problem seems to be unreported).
I'm somewhat familiar with Python (not an expert, but I've written a few programs and I know the language passibly well). I haven't gotten to the point of even compiling the PyKDE libraries, running into problems in kdecorecmodule.
I'm not sure, but I'm fairly certain that's a key module I can't just skip (a la what most people seem to suggest on the mailing list when the compile hits a problem). I'm probably going to have to edit the code, but there's something not right in editing autogenerated stubs - I need to see what's generating those incorrect entries.
--
Evan
|
[
Reply To This | View ]
|
Re: New Python Libraries
by Richard on Tuesday 17/Sep/2002, @15:12
|
"Nor am I alone (although this particular problem seems to be unreported)."
... so is the problem reported, or not?
|
[
Reply To This | View ]
|
Re: New Python Libraries
by Evan "JabberWokky" E. on Wednesday 18/Sep/2002, @00:05
|
I am not alone in having this sort of error in compilation (the sip generated code not aligning to the Qt API), but this problems with the wrapper for this particular call hasn't appeared on the list (or anywhere else via Google). The problem of one of the wrappers having this error has been reported, however, and the usual recommendation seems to be to just skip that module. Since this is a core module, I cannot do that.
Again, I'm not slamming this project. I've only tried on SuSE 7.3 and 8.0, and maybe SuSE has directories or library locations different than those that sip assumes. Or maybe sip is borked. Or maybe it's my fault somehow. It's just a fairly common problem according to what I've read, so my only observation is that the compilation process (which, as a side note, does not use autoconf but rather a python script) could be a bit more robust. YMMV.
The end result looks great - it's just a little rough to get it installed in my experience. My monitor died yesterday, so I haven't done anything with it today - maybe I'll have it running in the next twenty minutes :).
--
Evan
|
[
Reply To This | View ]
|
|
Re: New Python Libraries
by Marc Schmitt on Tuesday 17/Sep/2002, @10:54
|
Hi,
I'm packing sip/PyQt/PyKDE for SuSE Linux. I've also provided some .src.rpm
on sourceforge. ( http://sourceforge.net/project/showfiles.php?group_id=61057 ). Try to download the .src.rpms and compile them and bombard me with any questions that arise (English or German, what you prefer).
Also, feel free to post on the mailinglist at PyKDE@mats.gmd.de for any in-depth-questions.
:)
-Marc
|
[
Reply To This | View ]
|
Re: New Python Libraries
by Richard on Tuesday 17/Sep/2002, @15:11
|
What can I say, PyQt has worked for me for a very long time. I've only just recently (in the last couple of weeks) looked into PyKDE, and it worked out of the box too. Perhaps you're not using the latest Qt or KDE? There are always going to be some minor-version incompatibilities - some library developers out there seem to have no problem with changing APIs between minor versions...
And it certainly didn't take _12_ hours to compile on my relatively low-powered Pentium-II 350 .. what are you using, a 386???
|
[
Reply To This | View ]
|
Re: New Python Libraries
by Evan "JabberWokky" E. on Wednesday 18/Sep/2002, @00:15
|
:: Perhaps you're not using the latest Qt or KDE?
3.0.5 and 3.0.3. SuSE's RPMs.
:: And it certainly didn't take _12_ hours to compile on my relatively low-powered Pentium-II 350 .. what are you using, a 386???
A dual 700 PIII. And it certainly took me 12 hours of elapsed clock time - but only several hours (maybe 4 to 5) actual compile time. I kicked off the build.py, waited several minutes, realized that takes a long time, came back an hour later, kicked off make, came back an hour later, did make install as root, etc, etc. Then I hit PyKDE, and it didn't work. Okay, start from scratch... repeat. Yeah - the actual compiles took a long time, but the compile process involved quite a bit of "waiting on user", and "user sighing, deleting directories, untarring, trying again" and "user downloading source rpms and trying those". :)
Again, I'm not slamming the project (although by the antagonistic tone here, I feel like I'm having to defend the fact that it didn't work for me). I'm sure it buttered your toast - it just didn't compile out of the tarball on a pretty vanilla SuSE install for me. Cest la vie.
--
Evan
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
