diff options
Diffstat (limited to 'bitbake/lib/bb/__init__.py')
-rw-r--r-- | bitbake/lib/bb/__init__.py | 12 |
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 | |||
27 | if sys.version_info < (2, 6, 0): | 27 | if 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 | |||
31 | class 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 | |||
30 | import os | 42 | import os |
31 | import logging | 43 | import logging |
32 | 44 | ||