Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Guillaume Tucker <gtucker@gtucker.io>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Onur Özkan" <work@onurozkan.dev>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	linux-doc@vger.kernel.org, workflows@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	automated-testing@lists.yoctoproject.org,
	"kernelci lists.linux.dev" <kernelci@lists.linux.dev>
Subject: Re: [PATCH 1/2] scripts: add TOML config to container tool
Date: Sat, 29 Aug 2026 10:56:47 +0200	[thread overview]
Message-ID: <faa022bc-bda5-47ee-9984-4e8ff067c6e1@gtucker.io> (raw)
In-Reply-To: <CANiq72k6T9Y_Vubih6pFMQBxju2xQq0VQkCXT1WL0qSyCXKxyA@mail.gmail.com>

Hi Miguel,

On 28/08/2026 7:35 pm, Miguel Ojeda wrote:
> On Fri, Aug 28, 2026 at 7:25 PM Guillaume Tucker <gtucker@gtucker.io> wrote:
>>
>> It states Python 3.9 which was already older than the 3.10 minimum
>> set when the container tool was merged.  Also my understanding is
>> that it's not a hard requirement for all the kernel tools, only for
>> building and producing a functioning kernel.  If I misunderstood this
> 
> I didn't check at the moment, but at least back when the "(optional)"
> tag was removed, it was only required for certain configurations from
> what I understand (I am not sure why the tag was removed).
> 
> In any case, it is nice if we could just say that it is required -- it
> is quite useful to have around, especially due to its standard
> library.

OK so I'll leave this part as-is for now unless someone makes a
strong case for downgrading to v3.9, thanks for confirming.

> And regarding the minimum version, it would be nice to eventually have
> a single minimum for all Python scripts, no? Debian oldstable is
> already at 3.11, so I think we could perhaps bump the minimum already.
> And Debian stable is 3.13, which from your list would be enough for
> everything on your list, right? So we could perhaps set that as the
> actual minimum for everything in the future.

I was wondering about this too, especially since v3.10 is soon going
to reach end-of-life which means no more security patches.  In
principle newer, version should be backwards compatible so if we just
bumped the minimum to v3.13 older scripts that were written for v3.9
should still work - but it'd be nice to have a way to test that.

Well that's beyond this series anyway, maybe something for KernelCI?

Guillaume


  reply	other threads:[~2026-08-29  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 10:05 [PATCH 1/2] scripts: add TOML config to container tool Guillaume Tucker
2026-08-24 10:05 ` [PATCH 2/2] Documentation: dev-tools: update container.rst with config file Guillaume Tucker
2026-08-24 10:55   ` Guillaume Tucker
2026-08-28  6:35     ` Guillaume Tucker
2026-08-28  6:39 ` [PATCH 1/2] scripts: add TOML config to container tool Guillaume Tucker
2026-08-28 16:29 ` Nicolas Schier
2026-08-28 17:25   ` Guillaume Tucker
2026-08-28 17:35     ` Miguel Ojeda
2026-08-29  8:56       ` Guillaume Tucker [this message]
2026-08-29 11:01         ` Miguel Ojeda
2026-09-04 16:29         ` Nicolas Schier
2026-08-29  9:02       ` Guillaume Tucker
2026-08-29 10:57         ` Miguel Ojeda
2026-09-02 10:26     ` Guillaume Tucker
2026-09-03 20:27       ` Nathan Chancellor

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=faa022bc-bda5-47ee-9984-4e8ff067c6e1@gtucker.io \
    --to=gtucker@gtucker.io \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=corbet@lwn.net \
    --cc=kernelci@lists.linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@kernel.org \
    --cc=work@onurozkan.dev \
    --cc=workflows@vger.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