bitbake/exceptions: Handle reports from the field of exception code failures
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 24 May 2012 13:23:44 +0000 (14:23 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 25 May 2012 10:15:12 +0000 (11:15 +0100)
commita7bf06f902465ed9d7d0917856238b8f1ce910b4
tree520f71c736f4a7626418c4f168f0a42a14e73448
parent86c7f20f0c59229da1097260209aa9fb8053735d
bitbake/exceptions: Handle reports from the field of exception code failures

Despite using python 2.6, there have been reports of issues where
bitbake is printing tracebacks with errors in the exception handling
code. This was masking the real error.

Since we need to do whatever we can to give the user good feedback about
errors, detect the tuple instead of namedtuple case and don't fault
in the exception handler but just give up trying to traceback any further.

In the reported cases, this gives a message the user can then understand.

(Bitbake rev: 9ec0429271e68527a55fc123dea5a1b959c6ec3b)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/lib/bb/exceptions.py