From: Trevor Gamblin <tgamblin@baylibre.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org,
Ross Burton <ross.burton@arm.com>,
Tim Orling <tim.orling@konsulko.com>
Subject: Re: [OE-core][PATCH 0/5 v2] python3: upgrade 3.13.9 -> 3.14.2
Date: Thu, 8 Jan 2026 08:47:49 -0500 [thread overview]
Message-ID: <e08f4462-d60d-41e4-9345-abab1cddbd57@baylibre.com> (raw)
In-Reply-To: <18883AAF7D8D6C1A.2355985@lists.openembedded.org>
On 2026-01-06 14:22, Trevor Gamblin via lists.openembedded.org wrote:
>
> On 2026-01-06 04:39, Alexander Kanavin wrote:
>> On Mon, 5 Jan 2026 at 15:18, Trevor Gamblin <tgamblin@baylibre.com>
>> wrote:
>>>>> Maybe. I tried all of this locally (on a F43 system, which includes
>>>>> 3.14.2 as of writing), and after I sourced the pokysdk script, the
>>>>> interpreter on my path changed to version 3.13.4. Seems that the
>>>>> install-buildtools script is (at least for me) resulting in a 3.13.4
>>>>> version is getting pulled in. I'd think maybe something got
>>>>> contaminated
>>>>> somehow from my cache, but there'd be newer 3.13.x versions for it to
>>>>> grab if that were the case.
>>>> install-buildtools brings in python 3.13 into PATH, as that's what is
>>>> inside the buildtools tarball. That is expected and won't change until
>>>> after 3.14 lands in core, and new buildtools is produced with it.
>>>>
>>>> The mystery is why the test first gets 3.14 from running python3 (that
>>>> comes from the sdk installation), then right after that 3.13 from
>>>> running maturin (that comes from buildtools).
>>> Ross and/or Tim, any thoughts?
>> I looked into it a bit. I believe the issue was outdated maturin, with
>> the 1.9.4 -> 1.10.2 update having landed in master it goes away. This
>> patchset can be re-taken into testing without modifications.
> Thanks for looking at this again.
>
> I did see that there was an upgrade submitted to move python from
> 3.13.9 -> 3.13.11, so if that goes in first then I'll still need to
> rebase this.
That upgrade is now on master-next, so I will rebase and re-send this
series.
- Trevor
>>
>> Alex
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#228922): https://lists.openembedded.org/g/openembedded-core/message/228922
> Mute This Topic: https://lists.openembedded.org/mt/116859136/7611679
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [tgamblin@baylibre.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2026-01-08 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 13:47 [OE-core][PATCH 0/5 v2] python3: upgrade 3.13.9 -> 3.14.2 Trevor Gamblin
2025-12-19 13:47 ` [PATCH 1/5 v2] python3: upgrade 3.13.9 -> 3.14.0 Trevor Gamblin
2025-12-19 13:47 ` [PATCH 2/5 v2] python3targetconfig: export _PYTHON_PROJECT_BASE Trevor Gamblin
2025-12-19 13:47 ` [PATCH 3/5 v2] python_pep517: add --prefix to nativepython3 call Trevor Gamblin
2025-12-19 13:47 ` [PATCH 4/5 v2] python3: upgrade 3.14.0 -> 3.14.2 Trevor Gamblin
2025-12-19 13:47 ` [PATCH 5/5 v2] python3: add _py_warnings, annotationlib to core Trevor Gamblin
2025-12-22 8:11 ` [OE-core][PATCH 0/5 v2] python3: upgrade 3.13.9 -> 3.14.2 Mathieu Dubois-Briand
2025-12-22 18:36 ` Trevor Gamblin
2025-12-22 19:33 ` Alexander Kanavin
2025-12-22 19:52 ` Trevor Gamblin
2025-12-22 20:00 ` Alexander Kanavin
2026-01-05 14:17 ` Trevor Gamblin
2026-01-06 9:39 ` Alexander Kanavin
2026-01-06 19:22 ` Trevor Gamblin
[not found] ` <18883AAF7D8D6C1A.2355985@lists.openembedded.org>
2026-01-08 13:47 ` Trevor Gamblin [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=e08f4462-d60d-41e4-9345-abab1cddbd57@baylibre.com \
--to=tgamblin@baylibre.com \
--cc=alex.kanavin@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=tim.orling@konsulko.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