https://bugs.kde.org/show_bug.cgi?id=401512
--- Comment #2 from Maurizio Paolini <paol...@dmf.unicatt.it> ---
The following diff:
-----------------------------------------------------
$ git diff
diff --git a/scripting/python_scripter.cc b/scripting/python_scripter.cc
index 62a7409b..57e09255 100644
--- a/scripting/python_scripter.cc
+++ b/scripting/python_scripter.cc
@@ -531,6 +531,10 @@ ObjectImp* PythonScripter::calc( CompiledPythonScript&
script, const Args& args
};
tuple argstup( argstuph );
+// workaround?
+//
+ Py_INCREF (argstup.ptr());
+
handle<> reth( PyEval_CallObject( calcfunc.ptr(), argstup.ptr() ) );
// object resulto = calcfunc( argstup );
// handle<> reth( PyEval_CallObject( calcfunc.ptr(), args ) );
-----------------------------------------------------
seems to "work around" the reported issue. I do not know if this is a real fix
because I have no experience with boost, but at least allows to use python
scripting that otherwise seems to be completely broken (see the attached kig
example)
--
You are receiving this mail because:
You are watching all bug changes.
