* [PATCH] utils.py: Once we've printed errors messages, suppress the backtrace
@ 2012-08-22 19:02 Richard Purdie
0 siblings, 0 replies; only message in thread
From: Richard Purdie @ 2012-08-22 19:02 UTC (permalink / raw)
To: bitbake-devel
Adding a generic backtrace to better_compile and better_exec is pointless,
therefore reraise the exception as a bb.BBHandledException so the
generic code doesn't confuse the user even more.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/bitbake/lib/bb/utils.py b/bitbake/lib/bb/utils.py
index e0ef63c..82dab6b 100644
--- a/bitbake/lib/bb/utils.py
+++ b/bitbake/lib/bb/utils.py
@@ -216,7 +216,8 @@ def better_compile(text, file, realfile, mode = "exec"):
for line in body:
logger.error(line)
- raise
+ e = bb.BBHandledException(e)
+ raise e
def better_exec(code, context, text = None, realfile = "<code>"):
"""
@@ -231,7 +232,7 @@ def better_exec(code, context, text = None, realfile = "<code>"):
code = better_compile(code, realfile, realfile)
try:
exec(code, _context, context)
- except Exception:
+ except Exception as e:
(t, value, tb) = sys.exc_info()
if t in [bb.parse.SkipPackage, bb.build.FuncFailed]:
@@ -280,7 +281,8 @@ def better_exec(code, context, text = None, realfile = "<code>"):
nexttb = tb.tb_next
level = level + 1
- raise
+ e = bb.BBHandledException(e)
+ raise e
def simple_exec(code, context):
exec(code, _context, context)
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2012-08-22 19:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-08-22 19:02 [PATCH] utils.py: Once we've printed errors messages, suppress the backtrace Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox