Page MenuHomeDevCentral

Extract Python error from an exception with traceback
ClosedPublic

Authored by dereckson on May 13 2017, 11:41.
Tags
None
Referenced Files
F53538834: D984.diff
Sat, Oct 10, 18:24
Unknown Object (File)
Fri, Oct 9, 16:30
Unknown Object (File)
Wed, Oct 7, 05:37
Unknown Object (File)
Wed, Oct 7, 04:36
Unknown Object (File)
Mon, Oct 5, 20:47
Unknown Object (File)
Mon, Oct 5, 14:49
Unknown Object (File)
Sun, Oct 4, 17:30
Unknown Object (File)
Sat, Oct 3, 15:19
Subscribers

Details

Summary

.+surname and .+givenname can sometimes fail with a
pywikibot.data.api.APIError thrown.

If we were in a pure Python context we could nicely catch
those errors.

Currently, from our TCL interpreter, we instead receive a text output.

A callback method is provided to parse this output to print error.

Fixes T1203.

Test Plan

With a test_exception raising a TypeError containing the text of the actual error
(so we can be sure we catch the REAL exception, not an embedded text looking like an exception):
run_command "python /home/surfboard/bin/test_exception" print_command_callback print_python_error_callback {dcc 14}
run_command "python /home/surfboard/bin/test_exception" print_command_callback print_python_error_callback {quick #pentacle}

Diff Detail

Repository
rVIPER ViperServ scripts
Lint
Lint Not Applicable
Unit
Tests Not Applicable