summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/python/python3/0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2023-02-17 12:09:33 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-02-19 07:48:28 +0000
commit42f4f740b1d6305b0636e232cc5e2c808285059c (patch)
tree06165592dfa620f5385dace063bea5fb88bae874 /meta/recipes-devtools/python/python3/0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch
parent149ea9db9645e29e29914ff7fab6c67237f7debc (diff)
downloadpoky-42f4f740b1d6305b0636e232cc5e2c808285059c.tar.gz
bitbake: cookerdata: Improve early exception handling
Martin Jansa reported that if you put a syntax error into an imported module such as qa.py in OE, no error is shown. Part of the issue appears to be that the catch_parse_error() decorator only catches certain exceptions and SyntaxError isn't one of them. As far as I can tell we should remove all the special cases and use the more advanced code in all cases, not just expansion errors. I confirmed this now prints a proper error message for a qa.py syntax error. (Bitbake rev: 2365d891847f8e73d1c4661ddfdab8818ff619dc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python/python3/0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch')
0 files changed, 0 insertions, 0 deletions