Re: [yocto] Arch Linux - Python Newer than Recommend i.e. post 3.12
Nicholas Krause <[email protected]>
| Newsgroups | org.yoctoproject.lists.yocto |
|---|---|
| Message-ID | <[email protected]> |
Greetings, Please forget. I've switched to scrathgap which works fine. Kirkenstone is frozen so I would not worry about my previous concerns. Nick On 2/22/26 12:58 AM, Nicholas Krause wrote: > Greetings, > Pinging this email as its been a few weeks and not sure if the patches > have been backported. > > Thanks, > Nick > > On 2/6/26 5:49 PM, Nicholas Krause wrote: >> 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 >>> <[email protected]> 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 >>> >> >