Page MenuHomeDevCentral

Extract Python error from an exception with traceback
ClosedPublic

Authored by dereckson on May 13 2017, 11:41.
Tags
None
Referenced Files
F56942346: D984.id2515.diff
Wed, Nov 11, 07:30
F56882009: D984.diff
Tue, Nov 10, 09:37
F56794282: D984.diff
Mon, Nov 9, 10:16
F56597205: D984.id2594.diff
Sat, Nov 7, 13:40
F56489907: D984.diff
Fri, Nov 6, 12:54
F56447771: D984.id2515.diff
Fri, Nov 6, 06:29
F56447759: D984.id2594.diff
Fri, Nov 6, 06:29
F56447751: D984.id.diff
Fri, Nov 6, 06:29
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