From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rob.woolley@windriver.com, bitbake-devel@lists.openembedded.org
Cc: alex.kanavin@gmail.com
Subject: Re: [bitbake-devel] [PATCH v2 01/13] bitbake-setup: Resolve unused loop control variables
Date: Wed, 01 Apr 2026 22:44:21 +0100 [thread overview]
Message-ID: <fc03b4e55fe901ef7b5ac103340e929af8edd5af.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260331160703.3137930-2-rob.woolley@windriver.com>
On Tue, 2026-03-31 at 09:06 -0700, Rob Woolley via lists.openembedded.org wrote:
> The ruff lint tool reported loop control variables that were
> not being used:
> B007 Loop control variable `dirs` not used within loop body
>
> Adding underscore as a prefix helps indicate that it is not
> being used inside the loop.
>
> Signed-off-by: Rob Woolley <rob.woolley@windriver.com>
> ---
> bin/bitbake-setup | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/bin/bitbake-setup b/bin/bitbake-setup
> index b02cbc2b1..304fbe6cc 100755
> --- a/bin/bitbake-setup
> +++ b/bin/bitbake-setup
> @@ -134,7 +134,7 @@ def commit_config(config_dir):
> def _write_layer_list(dest, repodirs):
> layers = []
> for r in repodirs:
> - for root, dirs, files in os.walk(os.path.join(dest,r)):
> + for root, _dirs, files in os.walk(os.path.join(dest,r)):
> if os.path.basename(root) == 'conf' and 'layer.conf' in files:
> layers.append(os.path.relpath(os.path.dirname(root), dest))
> layers_f = os.path.join(dest, ".oe-layers.json")
I'd suggest just using "_" alone as the name as that is how we do it everywhere else.
Cheers,
Richard
next prev parent reply other threads:[~2026-04-01 21:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 16:06 [PATCH v2 00/13] bitbake-setup PyPI Packaging Rob Woolley
2026-03-31 16:06 ` [PATCH v2 01/13] bitbake-setup: Resolve unused loop control variables Rob Woolley
2026-04-01 21:44 ` Richard Purdie [this message]
2026-03-31 16:06 ` [PATCH v2 02/13] bitbake-setup: Fix ambiguous variable names Rob Woolley
2026-03-31 16:06 ` [PATCH v2 03/13] bitbake-setup: Set function default to None Rob Woolley
2026-04-01 21:43 ` [bitbake-devel] " Richard Purdie
2026-03-31 16:06 ` [PATCH v2 04/13] bitbake-setup: Add checks for version information Rob Woolley
2026-03-31 16:06 ` [PATCH v2 05/13] bitbake-setup: Add version option Rob Woolley
2026-03-31 16:06 ` [PATCH v2 06/13] bitbake-setup: Add the conditional script stanza Rob Woolley
2026-03-31 16:06 ` [PATCH v2 07/13] bitbake-setup: Add version check and catch exceptions Rob Woolley
2026-03-31 16:06 ` [PATCH v2 08/13] bitbake: Add checks for importing bb module Rob Woolley
2026-03-31 16:06 ` [PATCH v2 09/13] pypi: Add PyPI packaging for bitbake-setup Rob Woolley
2026-03-31 16:07 ` [PATCH v2 10/13] pypi: Add packaging documentation for developers Rob Woolley
2026-03-31 16:07 ` [PATCH v2 11/13] gitignore: Ignore temporary staging directory Rob Woolley
2026-03-31 16:07 ` [PATCH v2 12/13] lib: Vendorize bundled third-party libraries under bb._vendor Rob Woolley
2026-03-31 16:07 ` [PATCH v2 13/13] bb: Move codegen.py inside module Rob Woolley
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=fc03b4e55fe901ef7b5ac103340e929af8edd5af.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=rob.woolley@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox