From: "Paul Barker" <paul@pbarker.dev>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH 0/1] Substitute '~' when naming anonymous functions
Date: Tue, 20 Jul 2021 18:22:01 +0100 [thread overview]
Message-ID: <20210720182201.040efd99.paul@pbarker.dev> (raw)
In-Reply-To: <20210720171628.23394-1-paul@pbarker.dev>
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
On Tue, 20 Jul 2021 18:16:27 +0100
"Paul Barker" <paul@pbarker.dev> wrote:
> 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(-)
>
It helps if I include the URL rather than just leaving a dead
reference...
[1]: https://layers.openembedded.org/layerindex/layerupdate/9144821/
Thanks,
--
Paul Barker
https://pbarker.dev/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
prev parent reply other threads:[~2021-07-20 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 17:16 [PATCH 0/1] Substitute '~' when naming anonymous functions Paul Barker
2021-07-20 17:16 ` [PATCH 1/1] parse/ast: " Paul Barker
2021-07-20 17:22 ` Paul Barker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210720182201.040efd99.paul@pbarker.dev \
--to=paul@pbarker.dev \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.