Page MenuHomeDevCentral

Extract Python error from an exception with traceback
ClosedPublic

Authored by dereckson on May 13 2017, 11:41.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 17, 19:43
Unknown Object (File)
Thu, Nov 7, 17:21
Unknown Object (File)
Tue, Nov 5, 06:59
Unknown Object (File)
Sat, Oct 26, 05:23
Unknown Object (File)
Oct 20 2024, 04:23
Unknown Object (File)
Oct 18 2024, 11:55
Unknown Object (File)
Oct 18 2024, 11:54
Unknown Object (File)
Oct 18 2024, 10:35
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
No Lint Coverage
Unit
No Test Coverage
Branch
print_python_error_callback (branched from master)
Build Status
Buildable 1530
Build 1778: arc lint + arc unit