From: Nicholas Krause <xerofoify@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Arch Linux - Python Newer than Recommend i.e. post 3.12
Date: Fri, 6 Feb 2026 17:49:35 -0500 [thread overview]
Message-ID: <13ceffeb-db33-489d-b36e-81868b778fc8@gmail.com> (raw)
In-Reply-To: <F1186EBC-365D-4CC0-8BAE-3837F922BE3B@arm.com>
Greetings,
I'm on kirkenstone currently. So backporting the patches is probably
best. However, what's the longterm strategy around this as its been a
program for several years on more bleeding edge distributions i.e. Arch?
Even when were talking mainline its a problem with Arch sometimes.
Thanks,
Nick
On 2/5/26 5:40 AM, Ross Burton wrote:
> On 5 Feb 2026, at 02:37, Nicholas Krause via lists.yoctoproject.org <xerofoify=gmail.com@lists.yoctoproject.org> wrote:
>> _pickle.PicklingError: Can't pickle local object <function AsyncServer.serve_as_process.<locals>.run at 0x7fea88598a90>
>> when serializing dict item '_target'
>> when serializing multiprocessing.context.Process state
>>
>> Due to being on Python 3.14. I would prefer not to have to use a backwards supported penv for Yocto alone. Does anyone have any experience with working on Arch and how to avoid these issues without either dealing with penv or yay for getting a older version of python, pre 3.12 I believe.
>
> There’s a number of fixes for the 3.14 changes to multiprocessing in git, so you likely need to backport those. What version of Yocto are you using?
>
> Ross
>
next prev parent reply other threads:[~2026-02-06 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 2:39 Arch Linux - Python Newer than Recommend i.e. post 3.12 Nicholas Krause
2026-02-05 9:46 ` [yocto] " Alexander Kanavin
2026-02-05 10:40 ` Ross Burton
2026-02-06 22:49 ` Nicholas Krause [this message]
2026-02-08 21:09 ` Hugh Manning
2026-02-22 5:58 ` Nicholas Krause
2026-02-22 7:15 ` Nicholas Krause
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=13ceffeb-db33-489d-b36e-81868b778fc8@gmail.com \
--to=xerofoify@gmail.com \
--cc=Ross.Burton@arm.com \
--cc=yocto@lists.yoctoproject.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