public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: Nicolas Schier <nsc@kernel.org>, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 0/3] scripts/container: Minor fixups suggested by ruff
Date: Fri, 23 Jan 2026 16:46:39 -0700	[thread overview]
Message-ID: <20260123234639.GB206716@ax162> (raw)
In-Reply-To: <02fe1347-0124-45be-9b8a-7a439ce48a38@gtucker.io>

On Fri, Jan 23, 2026 at 09:26:20PM +0100, Guillaume Tucker wrote:
> Hi Nathan,
> 
> On 23/01/2026 12:27 am, Nathan Chancellor wrote:
> > Hi all,
> > 
> > This series fixes a few warnings that I see when running
> > 
> >    $ ruff check --select C4,RUF scripts/container
> > 
> > which were the few warnings from my personal ruff.toml that seemed most
> > interesting.
> > 
> > I will apply these on top of the initial scripts/container change.
> > 
> > ---
> > Nathan Chancellor (3):
> >        scripts/container: Turn runtimes class variable into a tuple
> >        scripts/container: Use list comprehension in get_names()
> >        scripts/container: Use iterable unpacking for _get_opts()
> > 
> >   scripts/container | 10 ++++++----
> >   1 file changed, 6 insertions(+), 4 deletions(-)
> > ---
> > base-commit: 6eac13c876805f61bbb588eaff5ada0b6dc603e8
> > change-id: 20260122-scripts-container-ruff-fixes-4d38fc92771a
> 
> LGTM - some of these things are arguably more a matter of individual
> taste than absolute best practices but it's good to have a
> well-defined code quality standard.  I typically use Pylint,
> Pycodestyle and Mypy, not Ruff or Black.  So for the whole series:
> 
> Reviewed-by: Guillaume Tucker <gtucker@gtucker.io>

Thanks a lot for taking a look and providing the comments. I am going to
hold off on this series for a little bit to ponder on providing a
.ruff.toml file first to ensure we have a common understanding around
Python linting in the kernel, especially given a lot of these lints can
be opinionated as you mentioned.

Cheers,
Nathan

  reply	other threads:[~2026-01-23 23:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 23:27 [PATCH 0/3] scripts/container: Minor fixups suggested by ruff Nathan Chancellor
2026-01-22 23:27 ` [PATCH 1/3] scripts/container: Turn runtimes class variable into a tuple Nathan Chancellor
2026-01-23 20:34   ` Guillaume Tucker
2026-01-22 23:27 ` [PATCH 2/3] scripts/container: Use list comprehension in get_names() Nathan Chancellor
2026-01-23 20:38   ` Guillaume Tucker
2026-01-22 23:27 ` [PATCH 3/3] scripts/container: Use iterable unpacking for _get_opts() Nathan Chancellor
2026-01-23 20:45   ` Guillaume Tucker
2026-01-23 15:14 ` [PATCH 0/3] scripts/container: Minor fixups suggested by ruff Miguel Ojeda
2026-01-23 21:01   ` Nathan Chancellor
2026-01-23 23:55     ` Miguel Ojeda
2026-01-23 20:26 ` Guillaume Tucker
2026-01-23 23:46   ` Nathan Chancellor [this message]
2026-02-04  8:54 ` Masahiro Yamada

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=20260123234639.GB206716@ax162 \
    --to=nathan@kernel.org \
    --cc=gtucker@gtucker.io \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=nsc@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox