[Nathanaël]

To be more precise, it’s the oPyWorker.$methodreturn() method that seems to receive the sendError call :

[Nathanaël]

Hi @Götz Krija

Thanks for your answer.

In between, I found out about the new sample library and it’s working very well on my setup indeed.

Not sure what caused the original error in my previous test/own library (except that I used an object instead of an object reference for the pyWorker), but at least now I can copy the logic and good practices of the sample library.

[Nathanaël]

Yes, possibilité of using of WIA or SSO would be nice.

[Nathanaël]

Noted. Thanks Andreas.

[Nathanaël]

Sorry, let me clarify:

* the problem seems to be that when explicitely calling sendError from the Python script it calls $methodreturn instead of $methoderror in the Omnis object, thus preventing us from managing python catched exception in a controlled way.

[Nathanaël]

Hi Andreas.

Not sure what you mean, because the $methoderror and $methodreturn functions of the Python Worker Object are effectively called asynchronously.

As discussed below, the problem seems to be that we are not able to explicitely call sendError from the Python script (thus the Omnis object’s $methoderror function), in a controlled / catched exception.

[Nathanaël]

@Götz Krija

Thanks for raising the fault.

Indeed I wrote another Python script that deliberately raises an exeption that is not catched, and it is actually calling the $methoderror method in the PyWorker object this time.

But that’s not practical, to be honest, because I would rather have the ability to catch exceptions in the python script, and use the sendError() method if necessary.