summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/__init__.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2012-01-09 17:01:51 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-01-10 17:40:43 +0000
commita5463088fe57462bf681b648d21212808454fc2a (patch)
treee3412641a6d15ef93b55f06e14ff51c45fef402e /bitbake/lib/bb/__init__.py
parente4a365098a9550facae9af069d4b58770dabfd91 (diff)
downloadpoky-a5463088fe57462bf681b648d21212808454fc2a.tar.gz
bitbake: Add BBHandledException exception class
We have a problem knowing when to show the user debug information and when not to since the code has already shown the user suitable information about why a failure is occurring. This patch adds a bb.BBHandledException exception class which can be used to identify those exceptions which don't need further explanation to the user. This patch uses this class for the bb.providers exceptions and ensures the command handling code correctly filters the exceptions meaning that "bitbake invalid" now shows an simple error message and not a python traceback. [YOCTO #1141 partial] (Bitbake rev: eac9249b40ae1e3aa21e016010c862664e59a8d4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/__init__.py')
-rw-r--r--bitbake/lib/bb/__init__.py12
1 files changed, 12 insertions, 0 deletions
diff --git a/bitbake/lib/bb/__init__.py b/bitbake/lib/bb/__init__.py
index 5dc959c7e5..81f83c88d5 100644
--- a/bitbake/lib/bb/__init__.py
+++ b/bitbake/lib/bb/__init__.py
@@ -27,6 +27,18 @@ import sys
27if sys.version_info < (2, 6, 0): 27if sys.version_info < (2, 6, 0):
28 raise RuntimeError("Sorry, python 2.6.0 or later is required for this version of bitbake") 28 raise RuntimeError("Sorry, python 2.6.0 or later is required for this version of bitbake")
29 29
30
31class BBHandledException(Exception):
32 """
33 The big dilemma for generic bitbake code is what information to give the user
34 when an exception occurs. Any exception inheriting this base exception class
35 has already provided information to the user via some 'fired' message type such as
36 an explicitly fired event using bb.fire, or a bb.error message. If bitbake
37 encounters an exception derived from this class, no backtrace or other information
38 will be given to the user, its assumed the earlier event provided the relevant information.
39 """
40 pass
41
30import os 42import os
31import logging 43import logging
32 44