Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc 3.5.0 cvs -march=athlon-xp OS: Linux python pyQT/pyKDE bindings are not build with python 2.4(cvs version) due to missing check during configure.
On Monday 05 July 2004 22:35, you wrote: > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > http://bugs.kde.org/show_bug.cgi?id=84531 > Summary: update for configure script needed for upcoming python > 2.4(CVS) > python pyQT/pyKDE bindings are not build with python 2.4(cvs version) due to missing check during configure. Could you be more specific? Cut and paste some output from configure if you need to. cheers,
that there's a check missing is easily observable when the configure script comes to a succession of python checks that resemble something like : checking for python 2.3 checking for python 2.2 . . . kde bindings will not be compiled type make to build as you can see it simply starts with 2.3 instead of 2.4 so i deduce the macros just don't check for version 2.4 though it would probably work just as well. i am aware of the fact that this is a rather unimportant problem - at least for the time being - yet it is an annoying one, because it causes me to downgrade my python to the 2.3 series. kind regards Maxim
python 2.4 isn't even beta yet. So who knows if the bindings will work with it when it's released? That's the reason we only check for versions we know it works with.
I've found the fix for myself now. To be honest i can't quite follow you argument Stephan, as we are talking about cvs HEAD repositories here anyway. Those are never considered stable or - sometimes - even workable. they are just there to try out THE NEW STUFF(tm). And compatibility testing with a new version of python (that is striving to maintain API and ABI continuity, btw) IMHO qualifies for this goal. After all, wouldn't it be good if the bindings would work when python 2.4 goes final instead of possibly a few weeks of debugging later ? However these are your policies and if you favour stability over cutting edge it is your decision to make. just compiled and tested it - no problems here. the fixes to make are in kdebindings/configure at 33480, 33483 and 40933, 40936, where you need to change the ""2.3"" into ""2.4"" - just for those who want to try out. best regards Maxim
closing as resolved
*** Bug 88198 has been marked as a duplicate of this bug. ***