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)
Sat, Oct 11, 03:00
Unknown Object (File)
Thu, Oct 9, 11:05
Unknown Object (File)
Thu, Oct 9, 11:04
Unknown Object (File)
Sun, Oct 5, 01:19
Unknown Object (File)
Sat, Oct 4, 20:40
Unknown Object (File)
Sat, Oct 4, 07:29
Unknown Object (File)
Sat, Oct 4, 04:08
Unknown Object (File)
Sat, Oct 4, 03:50
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