Bug 231138 - disconnect of signals not implemented in krosspython
Summary: disconnect of signals not implemented in krosspython
Status: RESOLVED UNMAINTAINED
Alias: None
Product: bindings
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Sauer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 20:10 UTC by Joris Guisson
Modified: 2024-05-06 18:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Joris Guisson 2010-03-17 20:10:46 UTC 
Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Ubuntu Packages

The problem is this function in pythonextension.cpp:

Py::Object PythonExtension::doDisconnect(const Py::Tuple&)
{
    //TODO
    return PythonType<bool>::toPyObject(false);
}

This means that if you connect to a signal in your script you can't disconnect and if you remove the script the function connect to it still gets called when the signal is emitted, which is even worse.
Comment 1 Sebastian Sauer 2010-04-10 23:45:11 UTC 
assign to me
Comment 2 Justin Zobel 2021-03-09 05:24:45 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 3 Christoph Cullmann 2024-05-06 18:09:56 UTC 
The bindings we had are no longer maintained and got removed with either KF5 or KF6, depending on the language.