Page MenuHomeDevCentral

Extract Python error from an exception with traceback
ClosedPublic

Authored by dereckson on May 13 2017, 11:41.
Tags
None
Referenced Files
F36185949: D984.id2515.diff
Tue, Jul 14, 18:25
F36146005: D984.id2515.diff
Tue, Jul 14, 14:45
F36071166: D984.id2594.diff
Tue, Jul 14, 06:47
F36019577: D984.id2515.diff
Tue, Jul 14, 00:42
Unknown Object (File)
Mon, Jul 13, 17:06
Unknown Object (File)
Mon, Jul 13, 07:55
Unknown Object (File)
Sun, Jul 12, 22:25
Unknown Object (File)
Sun, Jul 12, 22:21
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