René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Emit error messages via signals or return them from function calls (optionally)","articleBody":"Hello!\r\n\r\nWhenever a Python error occurs its description is sent to the stderr. I would like to emit a signal with error message instead. For instance, Qt’s own ECMAScript implementation, QJSEngine does not print to the stderr and instead returns a QJSValue containing error message, from which a string could be extracted and emitted via signal. It is very convenient.\r\n\r\nThe way I see it, this is how it could be done:\r\n\r\nWhen error occurs during `PythonQtObjectPtr::evalScript` or `PythonQtObjectPtr::call` calls return QString (wrapped in QVariant) instead of invalid QVariant. `PythonQt::hadError` would then tell whether this variant contains a “normal” string or an error message.\r\n\r\nOr perhaps you could even give errors their own struct, with fields like type, message, etc, and the return value could be tested like this:\r\n\r\n```c++\r\nPythonQtObjectPtr main_module = PythonQt::self()-\u003egetMainModule();\r\nQVariant result = main_module-\u003eevalScript (script);\r\nif (result.canConvert\u003cPythonQtErrorStruct\u003e())\r\n{\r\n    PythonQtErrorStruct error = result.value\u003cPythonQtErrorStruct\u003e();\r\n    emit errorOccured (error.type, error.message);\r\n}\r\n```\r\n\r\nI am aware that PythonQt lets redirection of stderr, but this is not the same. Plus in some cases user might want to emit error via signal, and in other to simply print it to stderr, so just bluntly redirecting the entire error output seems like a cumbersome solution.","author":{"url":"https://github.com/T-640","@type":"Person","name":"T-640"},"datePublished":"2021-06-27T16:21:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/51/pythonqt/issues/51"}