On Mon, 5 Jan 2026 at 15:18, Trevor Gamblin <[email protected]> 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. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#228882): https://lists.openembedded.org/g/openembedded-core/message/228882 Mute This Topic: https://lists.openembedded.org/mt/116859136/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
