Bug 211070 - Missing support in PyKDE4 for KIO.Job's result( KJob *) signal using the new stype API
Summary: Missing support in PyKDE4 for KIO.Job's result( KJob *) signal using the new ...
Alias: None
Product: bindings
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: kde-bindings
Depends on:
Reported: 2009-10-19 13:28 UTC by Luca Beltrame
Modified: 2010-06-28 23:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 4.5.0


Note You need to log in before you can comment on or make changes to this bug.
Description Luca Beltrame 2009-10-19 13:28:43 UTC
Version:            (using KDE 4.3.2)
Installed from:    SuSE RPMs

In parallel with the changes in recent versions of PyQt, PyKDE4 has adopted the new style API for signal/slot connections (i.e. OBJECT.SIGNAL.connect(SLOT) ). 
It works perfectly in most of the bindings, but in KIO.Job and derived subclasses there is no way to access the "result" signal without using the old API (SIGNAL("C++ signature")).

Given an example job:

get_job = KIO.get(KUrl("http://www.example.com/index.html"))

This is possible:

QtCore.QObject.connect(get_job, QtCore.SIGNAL("result( KJob *)"), some_slot)

while this raises an exception, as "result" is not present in "get_job":


As new-stype API is also used in other parts PyKDE4, this should - if technically possible - be addressed.
Comment 1 Luca Beltrame 2010-06-28 23:40:40 UTC
This is fixed in KDE SC 4.5 RC1 (tested with a simple program: the result slot gets called correctly instead of raising an exception). Closing.