From d73da22b0e332411ed5552d36910fe15f92c8fac Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 30 Mar 2016 20:52:56 +0100 Subject: bitbake: build/utils: Allow python functions to execute with real exception handling With the code as it stands today it not possible to execute a python function and get "normal" python exception handling behaviour. If a python function raises an exception, it forces a traceback to be printed and the exception becomes a FuncFailed exception. This adds in a parameter 'pythonexception' which allows standard python exceptions to be passed unchanged with no traceback. Ultimately we may want to change to this convention in various places but at least it means we can start to add sane functions now. (Bitbake rev: 85cf22fd0ed26bb7dc7738ef2a10441891f38ae2) Signed-off-by: Richard Purdie --- bitbake/lib/bb/utils.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'bitbake/lib/bb/utils.py') diff --git a/bitbake/lib/bb/utils.py b/bitbake/lib/bb/utils.py index 7ab8927608..e9ad68f2d7 100644 --- a/bitbake/lib/bb/utils.py +++ b/bitbake/lib/bb/utils.py @@ -372,7 +372,7 @@ def _print_exception(t, value, tb, realfile, text, context): finally: logger.error("\n".join(error)) -def better_exec(code, context, text = None, realfile = ""): +def better_exec(code, context, text = None, realfile = "", pythonexception=False): """ Similiar to better_compile, better_exec will print the lines that are responsible for the @@ -389,6 +389,8 @@ def better_exec(code, context, text = None, realfile = ""): # Error already shown so passthrough, no need for traceback raise except Exception as e: + if pythonexception: + raise (t, value, tb) = sys.exc_info() try: _print_exception(t, value, tb, realfile, text, context) -- cgit v1.2.3-54-g00ecf