From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rob.woolley@windriver.com,
"adrian.freihofer@gmail.com" <adrian.freihofer@gmail.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Cc: "alex.kanavin@gmail.com" <alex.kanavin@gmail.com>
Subject: Re: [bitbake-devel] [PATCH 10/11] bitbake-setup: Set function default to None
Date: Mon, 30 Mar 2026 23:51:46 +0100 [thread overview]
Message-ID: <0a7e52d678db59c049d3f45e4b3778bf8412cc46.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM8PR11MB56557582516EAE23B0AA187BE152A@DM8PR11MB5655.namprd11.prod.outlook.com>
On Mon, 2026-03-30 at 21:49 +0000, Rob Woolley via lists.openembedded.org wrote:
> Thanks for pointing this out.
>
>
> As far as Python 3.9 is concerned, it went end-of-life on October 31,
> 2025. I recognize that some supported hosts (like Debian 11 and RHEL
> 9) may have it by default. Do we increment the minimum Python
> version when the language runtime goes EOL or when the supported
> hosts do?
This is not an invitation to discuss the minimum python version this
close to release, particularly on a relatively trivial change like
this.
I'd rather just remove the typing than start trying to work out minimum
versions of different systems, how that combines with build tools, the
docs updates needed and so on.
Cheers,
Richard
next prev parent reply other threads:[~2026-03-30 22:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 18:57 BitBake Linting Errors Rob Woolley
2026-03-26 18:57 ` [PATCH 01/11] bitbake-setup: Remove extraneous variable from str.format() Rob Woolley
2026-03-26 18:57 ` [PATCH 02/11] bitbake-setup: Resolve unused loop control variables Rob Woolley
2026-03-26 18:57 ` [PATCH 03/11] bitbake-setup: Fix ambiguous variable names Rob Woolley
2026-03-26 18:57 ` [PATCH 04/11] bitbake-setup: Remove unused stdout variable Rob Woolley
2026-03-26 18:57 ` [PATCH 05/11] bitbake-setup: Replace f-string without placeholders Rob Woolley
2026-03-26 18:57 ` [PATCH 06/11] bitbake-setup: Remove unused Namespace import Rob Woolley
2026-03-26 18:57 ` [PATCH 07/11] bitbake-setup: Remove unused parser_settings_list Rob Woolley
2026-03-26 18:57 ` [PATCH 08/11] bitbake-setup: Fix linting error related to membership Rob Woolley
2026-03-26 18:57 ` [PATCH 09/11] bitbake-setup: Maintain exception chain Rob Woolley
2026-03-26 18:57 ` [PATCH 10/11] bitbake-setup: Set function default to None Rob Woolley
2026-03-30 16:34 ` [bitbake-devel] " adrian.freihofer
2026-03-30 21:49 ` Woolley, Rob
2026-03-30 22:51 ` Richard Purdie [this message]
2026-03-26 18:57 ` [PATCH 11/11] bitbake-setup: Sort and format imports 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=0a7e52d678db59c049d3f45e4b3778bf8412cc46.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=adrian.freihofer@gmail.com \
--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 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.