Substitute '~' when naming anonymous functions
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | parse/ast: Substitute '~' when naming anonymous functionslib/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] Substitute '~' when naming anonymous functions
When looking at meta-linux-mainline in the layer index I realised that the recipe version shown were out-of-date. The most recent update log [1] showed that the layer had failed to parse. Looking at the log it was obvious that this was due to the path in which the layer had been cloned, not due to any issue in the layer itself. As git repositories on sourcehut use '~' as a prefix to the username in the URL, this character ended up in the local path to the layer. When bitbake parsed the recipes in this layer, the '~' character ended up in the function name generated for an anonymous Python function. Since '~' isn't a valid character in a Python function name we got a pile of errors.
We already have a translation table to handle characters which aren't valid in Python function names, we just need to add '~' to the table.
Paul Barker (1):
parse/ast: Substitute '~' when naming anonymous functions
lib/bb/parse/ast.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 1 line
2.26.2